All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sverker Wiberg <Sverker.Wiberg@uab.ericsson.se>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: knfsd misses occasional writes (w/ WORKAROUND)
Date: Fri, 17 May 2002 14:32:36 +0200	[thread overview]
Message-ID: <3CE4F864.6E9B93AD@uab.ericsson.se> (raw)
In-Reply-To: <3CE250A5.47F71DF@uab.ericsson.se> <15586.20989.992591.474108@notabene.cse.unsw.edu.au> <3CE38E9D.986ACF7F@uab.ericsson.se> <20020516143441.A4322@laclinux.com> <3CE4DD8C.69C34A1B@uab.ericsson.se>

Sverker Wiberg wrote:

> Over here, we started to log the conversations, and saw the client
> opening a file, writing 272 bytes into it (one write), and then closing
> it, with the server replying full success all the time. printk()'s in
> knfsd and the vfs's generic_write() also reported that 272 bytes had
> been successfully written. Yet the file was truncated.
> 
> We switched from soft to hard mount: It didn't help. We are now
> experimenting with disabling SCSI's disconnect/reconnect feature. Are
> there any more straws to grasp at?

With one single knfsd thread running, the problem went away (for a price
in performance). This seems to indicate there is some kind of race
between the knfsd threads. 

/Sverker

      parent reply	other threads:[~2002-05-17 12: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
2002-05-17 10:38       ` Sverker Wiberg
2002-05-17 12:32         ` PROBLEM: knfsd misses occasional writes (w/ WORKAROUND) Sverker Wiberg
2002-05-17 12:32         ` Sverker Wiberg [this message]

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=3CE4F864.6E9B93AD@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 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.