public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sverker Wiberg <Sverker.Wiberg@uab.ericsson.se>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: PROBLEM: knfsd misses occasional writes
Date: Wed, 15 May 2002 14:12:21 +0200	[thread overview]
Message-ID: <3CE250A5.47F71DF@uab.ericsson.se> (raw)


Hello everyone, 

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
size when checking locally with `ls' (the clients reported total
success). With `asynch' instead, all files were correctly copied. 

I have seen this behaviour in 2.4.17 (UP and SMP builds, UP hardware) as
well as 2.4.18, when using the NFSv2 protocol. I have not tried 2.5.x
and NFSv3 yet. The full /etc/exports line is:

   /opt/telorb 172.16.0.0/255.255.0.0(rw,sync,no_wdelay)

Removing `no_wdelay' makes no difference.

The clients are all 2.4.17, and the relevant .config lines (for both
server and clients) are:

   CONFIG_NFS_FS=y
   CONFIG_NFS_V3=y
   CONFIG_ROOT_NFS=y
   CONFIG_NFSD=y
   CONFIG_NFSD_V3=y
   CONFIG_SUNRPC=y
   CONFIG_LOCKD=y
   CONFIG_LOCKD_V4=y

Reading the source (fs/nfsd/*) seems to show that knfsd tries to do the
right thing.

/Sverker Wiberg

             reply	other threads:[~2002-05-15 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 12:12 Sverker Wiberg [this message]
2002-05-15 12:18 ` PROBLEM: knfsd misses occasional writes 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
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=3CE250A5.47F71DF@uab.ericsson.se \
    --to=sverker.wiberg@uab.ericsson.se \
    --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