On Tue, 2001-10-09 at 20:06, René Rebe wrote: > Hi all. > > After I haven't used the kenel NFS server for a long time (needed to unmount devices > (ZIP, CDROM, ...) during exports - wich was/is not possible with the kernel NFS > server) I gave it a new try. (Need the extra performance and 64bit file-sizes) > > I use the 2.4.9 and 2.4.10 kernel and the 0.2.1 nfs-utils (glibc-2.1.3) to export > a 80 GB ReiserFS on a RAID array under RockLinux. > > NFS often mangles sym-link names to random garbage. > > e.g: > ln -s linux-2.4.10 linux > results in: > linux -> linux-2.4.10ot set? > next try: > linux -> linux-2.4.10USB?RCOM? "me too" :) Got a similar problem with ReiserFS server. Works most of the time, but sometimes file reads appear short, and random data corruption happens. The data on the server is fine -- doesn't get corrupted, but the client gets corrupted data over the wire. I've also tried 2.4.9 and 2.4.10. > > or the asm link creted by the make dep clean bzImage: > asm -> asm-i386RQ=y? > > I also get them with other files, and random *.nfs.* files very often, too. > > The ReiserFS is still intact and executing the commands on the server directly > results in a correct sym-link. Exactly the same problem here. > > Since I notices that there is a nfs-utils-0.3.3 package I will try it out and > report in more detail. But maybe there are some other advices or comments? I got 0.3.1. Same problem. On exactly the same hardware/kernel/clients/server, but using ext2, I've got no problem. I don't seem to have this problem on a non-stressed client. I only get this problem when there is enough traffic to cause >50% collisions on the cheap hub (at which point it slows down dramatically). It could simply be that the collisions aggravate the problem. I also get the problem with both NFS v2 and NFS v3, and I've played with the read/write sizes, timeouts, and soft and hard mounts. I have not tried the user-land NFS server. Because of the ReiserFS FAQ, I feel obliged to include these two lines: I've got this on multiple ReiserFS servers, and on no ext2 servers. I've used two different gcc's (to get around the RedHat gcc problem) > > René Rebe > > -- > René Rebe (Registered Linux user: #127875) > > eMail: rene.rene@gmx.net > rene.rebe@rocklinux.org > > Homepage: http://www.rene.rebe.myokay.net/ > > 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. > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Berend De Schouwer - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
