Re: PROBLEM: knfsd misses occasional writes
G Sandine (firstname.lastname@example.org)
Thu, 16 May 2002 14:34:41 -0600
On Thu, May 16, 2002 at 12:49:01PM +0200, Sverker Wiberg wrote:
> Neil Brown wrote:
> > On Wednesday May 15, Sverker.Wiberg@uab.ericsson.se wrote:
> > > When copying lots of small files from multiple NFS clients to a kNFSd
> > > filesystem (i.e. doing backup of a cluster), exported with `sync', I
> > > find that some few files (1 out of 1000) were silently truncated to zero
> no errors reported
> > How are you mounting the file systems on the clients?
> > The symptoms sound exactly like you are using "soft" mounts. "soft"
> > is a very bad mount option. Use "hard".
> > If you aren't using "soft", let me know and I will look harder.
> Errrm, I am using "soft" mounts, as I (we) want the clients to survive
> server restarts.
> But shouldn't those timeouts become errors over at the clients?
I have seen this too, with a file system exported with rw,no_root_squash
and mounted hard,intr. We were running vanilla 2.4.18 on the server
and clients. We have a text file on the server serving to record
employees' time, and one day the time clock file remained a text file
but was truncated to zero. All further punch ins/punch outs did not
record in the truncated file (user names, dates, and times should have
appended). Deleting and recreating the text file on a client returned
behavior to normal. No error messages whatsoever, and it has worked
fine for two weeks as we watch for the behavior to repeat.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/