From: Dan Yocum <yocum@fnal.gov>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: Null characters in files on NFS mounted volume....
Date: Tue, 14 May 2002 14:03:12 -0500 [thread overview]
Message-ID: <3CE15F70.7C8B8433@fnal.gov> (raw)
In-Reply-To: 200205141734.g4EHYnT32724@buggy.badula.org
Ion,
The apps are apache and plain old 'less,' so I bet they just use read().
And the problem hasn't cropped up again (yet) and hadn't cropped up in ~1
year with older kernels (specifically 2.4.5). I just upgraded to 2.4.18
last Thursday when it did start.
I'll change the options to hard and see if that makes any changes.
Thanks,
Dan
Ion Badulescu wrote:
>
> On Tue, 14 May 2002 09:41:39 -0500, Dan Yocum <yocum@fnal.gov> wrote:
> >> > 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.
> >>
> > Neil Brown wrote:
> >> 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
>
> In that case let me ask you this: is your application checking the return
> code of the read()? or are you using mmap() instead of read()?
>
> If read() returns zero-filled buffers without signalling an errors, it's
> a problem in the NFS client. That is, assumming it's not some bad interaction
> between XFS and the NFS server -- so try to clear up that possibility
> by mounting with the hard option.
>
> If you're using mmap(), then I don't even know how the system should tell
> you about the problem... I suppose it would be sending a SIGSEGV or SIGBUS
> signal, since it's ultimately a failing page fault, but I haven't tested it.
>
> > I suppose they could be hard.... I'll think about that.
>
> Yes, they _should_ be hard if you care about your data integrity.
>
> But that shouldn't stop us from fixing bugs in the 'soft' model, if they
> exist... which is why I'm asking you all these details. :-)
>
> Ion
>
> --
> It is better to keep your mouth shut and be thought a fool,
> than to open it and remove all doubt.
--
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
next prev parent reply other threads:[~2002-05-14 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 14:33 Null characters in files on NFS mounted volume Dan Yocum
2002-05-13 15:08 ` Trond Myklebust
2002-05-13 16:54 ` Dan Yocum
2002-05-14 6:47 ` Trond Myklebust
2002-05-14 14:22 ` Dan Yocum
2002-05-13 20:29 ` Neil Brown
2002-05-14 14:41 ` Dan Yocum
2002-05-14 17:34 ` Ion Badulescu
2002-05-14 19:03 ` Dan Yocum [this message]
2002-05-24 16:44 ` Dan Yocum
2002-05-24 21:34 ` Ion Badulescu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CE15F70.7C8B8433@fnal.gov \
--to=yocum@fnal.gov \
--cc=ionut@cs.columbia.edu \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.