public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kortus <sumix@atlas.cz>
To: linux-nfs@vger.kernel.org
Subject: Delay when writing to a file through pNFS
Date: Thu, 10 Jun 2010 21:09:09 +0200	[thread overview]
Message-ID: <4C113855.2080806@atlas.cz> (raw)

Hi,

I'm running a three-machine pNFS setup (MDS, DS and client on different 
virtual machines). When copying a file a mounted pNFS export or writing 
to a new file (with dd, for example), the write is delayed by 
approximately 15 seconds. When I write to a file that already exists, it 
works OK (there's no delay).

The NFS debug messages in kernel log (on the client) are showing that 
the client tries to write to the file, gets error -11 EAGAIN, waits 15 
seconds, then tries again successfully. I put a part of the kernel log 
concerning copying a small file to a pNFS export at 
http://charon.styxx.cz/tmp/pnfs/pnfs_write_log.txt

I have no idea what is the cause of the delays, so I hope someone could 
give me some advice concerning that. Thanks in advance.

Best regards,

Jiri Kortus

                 reply	other threads:[~2010-06-10 19:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C113855.2080806@atlas.cz \
    --to=sumix@atlas.cz \
    --cc=linux-nfs@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