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

[Dan Yocum <yocum@fnal.gov>]

Neil Brown wrote:
> 
> On Monday May 13, yocum@fnal.gov wrote:
> > 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.
> 
> I remembers long ago some referred to NFS as
>    Nulls Frequently Substituted
> because they were experiencing exactly this sort of thing, and it
> wasn't on Linux at all.

Ha!  :-)

I did find a similar occurence while googling
(http://www.geocrawler.com/archives/3/4/1998/11/0/59164/), reported back in
'98 on LinuxPPC, that produced similar results, but since this happened 3
times on the same day to 3 different machines, I thought I'd report it.


> 
> You wouldn't be using 'soft' mounts would you?


yup, automounted with these options:  

-rw,grpid,soft,intr,quota,nodev,nosuid,timeo=10,retrans=3


I suppose they could be hard....  I'll think about that.

Cheers,
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