Re: Re: 2.5.0 breakage even with fix?

Re: Re: 2.5.0 breakage even with fix?

[Jeff Merkey]

I am seeing file system corruption in NWFS in 2.5.0 with the patch.   It's
not a severe as
ext2 directly was, and is simply creating mirror mismatches between the FAT
and DIR
tables, and is easily recovered, but it is annoying.  I am also getting
"resource busy" during reboot when I try to reboot with a mounted NWFS
volume.

Jeff

----- Original Message -----
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: <viro@math.psu.edu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, November 23, 2001 6:05 PM
Subject: Re: 2.5.0 breakage even with fix?


> On 24 Nov 01 at 0:54, viro@math.psu.edu wrote:
> > Hi Al,
> >   I'm now running 2.5.0 with fix you posted - and now during dselect
> > run I received:
> >
> > Unpacking replacement manpages ...
> > EXT2-fs error (device ide0(3,3)): ext2_check_page: bad entry in
directory
> >   #3801539: unaligned directory entry - offset=0, inode=1801675088,
> >   rec_len=26465, name_len=101
> > Remounting filesystem read-only
> > rm: cannot remove directory `/var/lib/dpkg/tmp.ci': Read-only file
system
>
> Well, ncheck finished.
>
> debugfs: stat /var/lib/dpkg/tmp.ci
> Inode: 3801539  Type: directory  Mode: 0755  Flags: 0x0  Generation:
537829
> User:     0   Group:   0    Size: 4096
> File ACL: 0   Directory ACL: 0
> Links: 2  Blockcount: 8
> Fragment: Address: 0   Number: 0   Size: 0
> ctime: 0x3bfede00 -- Sat Nov 24 00:38:40 2001
> atime: dtto
> mtime: dtto
> BLOCKS:
> (0):7603845
> TOTAL: 1
>
> debugfs: cat /var/lib/dpkg/tmp.ci
> Package: diff
> Version: 2.7-28
> Section: base
> Priority: required
> Architecture: i386
> ...
>
> It does not look like a directory to me. Unfortunately, as we
> do not have coherent /dev/hda3 cache, I have no idea how to read
> real contents of /var/lib/dpkg/tmp.ci, but
> ls -l /var/lib/dpkg/tmp.ci/ reemited error message about
> ext2-fs error, so I think that it is real problem, and my tmp.ci directory
> contains some file contents instead. And I'm 100% sure that
> /var/lib/dpkg/tmp.ci was created with patched kernel :-(
>                                             Petr Vandrovec
>                                             vandrove@vc.cvut.cz
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: Re: 2.5.0 breakage even with fix?

[Jeff Merkey]

I fscked and vrepaired the NWFS volumes, and it seems to be OK now.  Might
have been
left over from the previous errors.  I will let you know if I see other
problems.

:-)

Jeff

----- Original Message -----
From: "Jeff Merkey" <jmerkey@timpanogas.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>; <viro@math.psu.edu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, November 23, 2001 5:14 PM
Subject: Re: Re: 2.5.0 breakage even with fix?


>
> I am seeing file system corruption in NWFS in 2.5.0 with the patch.   It's
> not a severe as
> ext2 directly was, and is simply creating mirror mismatches between the
FAT
> and DIR
> tables, and is easily recovered, but it is annoying.  I am also getting
> "resource busy" during reboot when I try to reboot with a mounted NWFS
> volume.
>
> Jeff
>
> ----- Original Message -----
> From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
> To: <viro@math.psu.edu>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Friday, November 23, 2001 6:05 PM
> Subject: Re: 2.5.0 breakage even with fix?
>
>
> > On 24 Nov 01 at 0:54, viro@math.psu.edu wrote:
> > > Hi Al,
> > >   I'm now running 2.5.0 with fix you posted - and now during dselect
> > > run I received:
> > >
> > > Unpacking replacement manpages ...
> > > EXT2-fs error (device ide0(3,3)): ext2_check_page: bad entry in
> directory
> > >   #3801539: unaligned directory entry - offset=0, inode=1801675088,
> > >   rec_len=26465, name_len=101
> > > Remounting filesystem read-only
> > > rm: cannot remove directory `/var/lib/dpkg/tmp.ci': Read-only file
> system
> >
> > Well, ncheck finished.
> >
> > debugfs: stat /var/lib/dpkg/tmp.ci
> > Inode: 3801539  Type: directory  Mode: 0755  Flags: 0x0  Generation:
> 537829
> > User:     0   Group:   0    Size: 4096
> > File ACL: 0   Directory ACL: 0
> > Links: 2  Blockcount: 8
> > Fragment: Address: 0   Number: 0   Size: 0
> > ctime: 0x3bfede00 -- Sat Nov 24 00:38:40 2001
> > atime: dtto
> > mtime: dtto
> > BLOCKS:
> > (0):7603845
> > TOTAL: 1
> >
> > debugfs: cat /var/lib/dpkg/tmp.ci
> > Package: diff
> > Version: 2.7-28
> > Section: base
> > Priority: required
> > Architecture: i386
> > ...
> >
> > It does not look like a directory to me. Unfortunately, as we
> > do not have coherent /dev/hda3 cache, I have no idea how to read
> > real contents of /var/lib/dpkg/tmp.ci, but
> > ls -l /var/lib/dpkg/tmp.ci/ reemited error message about
> > ext2-fs error, so I think that it is real problem, and my tmp.ci
directory
> > contains some file contents instead. And I'm 100% sure that
> > /var/lib/dpkg/tmp.ci was created with patched kernel :-(
> >                                             Petr Vandrovec
> >                                             vandrove@vc.cvut.cz
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>