[lkml]   [2001]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: File system Corruption with 2.4.16
On Sat, Dec 01, 2001 at 05:52:39PM -0700, Jeff Merkey wrote:
> ----- Original Message ----- From: "J Sloan" <>
> > Just to be positive, can you reproduce the problem without nwfs?
> Yes. The problem shows up on ext2 partitions only.
I destroyed a hard disk yesterday with 2.4.16, using ext3. A heavy load
(compiling The gimp and several other things) and everything came bad, symlinks
didn't work... (for exemple ln -s linux-2.4.17-pre2 linux did a link from linux
to linux either using linux-2.4.17-pre2 and /usr/src/linux-2.4.17-pre2.
> 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.
I had only one partition mounted at the moment (/dev/hda1 on / type ext3)

Just in case : debian sid, gcc 2.95.4, everything up to date.

We're living in a dangerous world, since 2.4.10...


/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Ingénieur développement \ / AGAINST HTML MAIL )))
\\\ 6, av. de la Belle Image X ///
\\\ 94440 Marolles en Brie / \ +33 6 8643 3085 ///
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.095 / U:3.604 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site