Re: File system Corruption with 2.4.16

Kenneth Johansson
2001-12-02T18:12:27Z

I had problems with symlinks also. This is what I know about it so far.

I only get/got this problem on a server running 2.4.10 using reiserfs and when the
files was used over NFS.
Once it got itself into this state it is possible to create symlinks by hand but when
untaring an archive 90% of all links was wrong. Doing the same on the server directly
showed no problem.

A reboot of the client did not help but rebooting the server did. I have since
upgraded to 2.4.16 but only run for a few hours the last time needed many days to show
this problem so it could still be there.

A nice program to use is symlinks that shows all links that points to a file not
existing
symlinks -r . | egrep "^dangling"

Charles-Edouard Ruault wrote:

> The symlink problem you're reporting is exactly what i've been experiencing among
> other things ...
> on both systems i had multiple ext2 partitions and one reseirfs partition.
> The problem showed up after a few days of uptime. Both machines where not heaviliy
> loaded and had no memory shortage.
> It looks like it also happened on my third system, which had only 2 ext2 partitions
> . I was able to clean up this one with fsck and rebooted safely to 2.4.14 ....
> Given the fact that i'm not the only one to see the problem with 2.4.16 i'll safely
> backtrack all my machines to 2.4.14 ...
> If i can be of any help to pinpoint the problem please let me know. But since i'm
> not a kernel hacker i don't think i'll be pluging into the sources myself on my own
> !
> Thanks for the feedback !
> Charles-Edouard Ruault
>
> Stephane Jourdois wrote:
>
> > On Sat, Dec 01, 2001 at 05:52:39PM -0700, Jeff Merkey wrote:
> > > ----- Original Message ----- From: "J Sloan" <jjs@pobox.com>
> > > > 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...
> >
> > Ciao,
> >
> > --
> > /// 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 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/