From: Sverker Wiberg <Sverker.Wiberg@uab.ericsson.se>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: knfsd misses occasional writes
Date: Thu, 16 May 2002 12:49:01 +0200 [thread overview]
Message-ID: <3CE38E9D.986ACF7F@uab.ericsson.se> (raw)
In-Reply-To: <3CE250A5.47F71DF@uab.ericsson.se> <15586.20989.992591.474108@notabene.cse.unsw.edu.au>
Neil Brown wrote:
>
> On Wednesday May 15, Sverker.Wiberg@uab.ericsson.se wrote:
> >
> > 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
^^^^^^^^
no errors reported
> > size when checking locally with `ls' (the clients reported total
> > success). With `asynch' instead, all files were correctly copied.
>
> 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?
/Sverker
next prev parent reply other threads:[~2002-05-16 10:49 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 [this message]
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
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=3CE38E9D.986ACF7F@uab.ericsson.se \
--to=sverker.wiberg@uab.ericsson.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).