Re: File system Corruption with 2.4.16

["Jeff Merkey" <jmerkey@timpanogas.org>]

----- Original Message -----
From: "J Sloan" <jjs@pobox.com>
To: "Jeff Merkey" <jmerkey@timpanogas.org>
Cc: "Charles-Edouard Ruault" <ce@ruault.com>; <linux-kernel@vger.kernel.org>
Sent: Saturday, December 01, 2001 4:54 PM
Subject: Re: File system Corruption with 2.4.16


> Jeff Merkey wrote:
>
> > I am seeing corruption on 2.4.16 (2.4.17-pre1/2) as well.  Whatever this
> > gentlemen is doing is making it show up quicker, but I am on my fourth
> > interation of fsck'ing 2.4.16 on my production server with NWFS builds.
I
> > am looking through Al Viros's inode code changes to see if there's hole
> > somewhere.  This problem appears to be related to low memory conditions.
I
> > see it when memory is getting low.  May be VM related as well.
>
> Just to be positive, can you reproduce the
> problem without nwfs?

Yes.  The problem shows up on ext2 partitions only.  I also have seen a
lockup in NWFS when
I have patched my FS into Linux.  The lockup indicates a deadlock in the
inode layers above
me.  I see this lockup when I have more than one file system mounted at a
time.  It does not happen
when only a single volume (superblock) has been mounted, only with
multiples.  Ditto the ext2
corruption.  It only shows up when more than one superblock is active.
Perhaps this will help
narrow down the problem.  Since I have a VFS of my own, I could help track
this down, but it
will be tommorrow, I am working on NWFS tools code today. :-)

Jeff

>
> cu
>
> jjs
>
> -
> 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/