Null characters in files on NFS mounted volume....

[Dan Yocum <yocum@fnal.gov>]

Hi all,

I've got a "New and Exciting" <tm> bug using 2.4.18 with Trond's client
patches (sans the rpc_tweaks dif), but I'm not sure it's a client side
problem.

This is an intermitent problem:  When attempting to read a file (any file)
on an NFS mounted volume, there appear to be "holes" in the file filled with
ASCII NULL characters.  Reading the file on the local machines shows no such
holes, and other NFS clients don't see the holes, either.  A simple
umount/remount solves the problem.

Oh, I should add that these are autofs mounted volumes.

We thought these might be network driver problems, but we're seeing it on
natsemi, acenic and eepro100 drivers, and I doubt they could all be flaky.

Any ideas?

Thanks,
Dan


-- 
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
yocum@fnal.gov, http://www.sdss.org
SDSS.  Mapping the Universe.

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs