public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: G Sandine <lkml@laclinux.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: knfsd misses occasional writes
Date: Thu, 16 May 2002 14:34:41 -0600	[thread overview]
Message-ID: <20020516143441.A4322@laclinux.com> (raw)
In-Reply-To: <3CE250A5.47F71DF@uab.ericsson.se> <15586.20989.992591.474108@notabene.cse.unsw.edu.au> <3CE38E9D.986ACF7F@uab.ericsson.se>

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.

Regards,
Gary S.

  parent reply	other threads:[~2002-05-16 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 12:12 PROBLEM: knfsd misses occasional writes Sverker Wiberg
2002-05-15 12:18 ` Neil Brown
2002-05-16 10:49   ` Sverker Wiberg
2002-05-16 11:39     ` Neil Brown
2002-05-16 16:48       ` Sverker Wiberg
2002-05-16 20:34     ` G Sandine [this message]
2002-05-17 10:38       ` Sverker Wiberg
2002-05-17 12:32         ` PROBLEM: knfsd misses occasional writes (w/ WORKAROUND) Sverker Wiberg
  -- strict thread matches above, loose matches on Subject: below --
2002-05-17  2:32 PROBLEM: knfsd misses occasional writes Neil Brown

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=20020516143441.A4322@laclinux.com \
    --to=lkml@laclinux.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox