Jeff Roberson wrote:
> I don't know of any general syncer issues outside of this.
Boot single user, run fsck, then halt.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
er: [EMAIL PROTECTED]
> > >
> > > On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
> > > > Hello,
> > > >
> > > > I have a problem with kernels, built the last couple of days, where
> > > > during shutdown sync
lo,
> > >
> > > I have a problem with kernels, built the last couple of days, where
> > > during shutdown syncer is "giving up" on buffers. During the next boot
> > > all filesystems are checked because of improper dismount. Here follow
> > >
uple of days, where
> > during shutdown syncer is "giving up" on buffers. During the next boot
> > all filesystems are checked because of improper dismount. Here follow
> > the exact messages I get:
> >
> > Waiting (max 60 seconds) for system process `vnlru&
On Tue, 2 Sep 2003, Tim Robbins wrote:
> > Rev.1.3 of ext2fs/fs.h (etc.) abuses B_LOCKED to do little more than
> > make the sync() ignore ext2fs's private buffers (its complications are
> > mainly to handle the resulting B_LOCKED buffers). It wants to brelse()
> > the buffers so that their BUF_
On Tue, 2 Sep 2003, Tim Robbins wrote:
> On Tue, Sep 02, 2003 at 05:10:48AM +1000, Bruce Evans wrote:
>
> > Apparently the bug fixed in ext2fs/fs.h revs 1.3, 1.4 and 1.6 (etc.)
> > was restored in rev.1.14. I think this is because B_LOCKED buffers
> > were ignored in the sync() in boot() and flus
On Tue, 2 Sep 2003, Jan Srzednicki wrote:
> On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
> > I have a problem with kernels, built the last couple of days, where
> > during shutdown syncer is "giving up" on buffers. During the next boot
> &
On Tue, Sep 02, 2003 at 05:10:48AM +1000, Bruce Evans wrote:
> Apparently the bug fixed in ext2fs/fs.h revs 1.3, 1.4 and 1.6 (etc.)
> was restored in rev.1.14. I think this is because B_LOCKED buffers
> were ignored in the sync() in boot() and flushed later when
> vfs_unmountall() calls ext2fs_un
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
> Hello,
>
> I have a problem with kernels, built the last couple of days, where
> during shutdown syncer is "giving up" on buffers. During the next boot
> all filesystems are checked because of
On Mon, 1 Sep 2003, Lefteris Chatzibarbas wrote:
> I have a problem with kernels, built the last couple of days, where
> during shutdown syncer is "giving up" on buffers. During the next boot
> all filesystems are checked because of improper dismount. Here follow
> th
Hello,
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is "giving up" on buffers. During the next boot
all filesystems are checked because of improper dismount. Here follow
the exact messages I get:
Waiting (max 60 seconds) for syst
In message <[EMAIL PROTECTED]> Dag-Erling Smorgrav writes:
: Matt Dillon <[EMAIL PROTECTED]> writes:
: > (2) the I/O for the buffer synchronization is initiated but interrupts
: > are winding up being disabled by the halt code due to holding Giant
: > and not sleeping (more likely). T
Matt Dillon <[EMAIL PROTECTED]> writes:
> (2) the I/O for the buffer synchronization is initiated but interrupts
> are winding up being disabled by the halt code due to holding Giant
> and not sleeping (more likely). That all I can think of. We've hit
> the interrupt disablement
13 matches
Mail list logo
