[lkml]   [2001]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: File system Corruption with 2.4.16
On Sun, 02 Dec 2001 19:11:27 +0100
Kenneth Johansson <> wrote:

> 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"

This general NFS v3 sym-link bug was fixed in 2.4.11 or .12 it was "only" caused
by a non-zero terminated string ...

btw. my 2.4.16 file-server using ReiserFS on a soft-raid5 device of 3 IBM
IDE disks has not yet shown a corruption (but could be a bit faster ...).

server1:~ # cat /proc/version
Linux version 2.4.16 (root@server1.localnet) (gcc version 2.95.3 20010315 (release)) #2 Tue Nov 27 18:58:48 CET 2001
server1:~ # uptime
7:54pm up 3 days, 4:02, 1 user, load average: 0.01, 0.03, 0.00


k33p h4ck1n6

René Rebe (Registered Linux user: #248718 <>)



Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
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:18    [W:0.091 / U:2.616 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site