From: Benny Halevy <bhalevy@panasas.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: pNFS timeouts
Date: Mon, 14 Jun 2010 10:11:30 -0400 [thread overview]
Message-ID: <4C163892.20201@panasas.com> (raw)
In-Reply-To: <20100614085157.GS17703@ics.muni.cz>
On Jun. 14, 2010, 4:51 -0400, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> Hi,
>
> I'm playing with pNFS (spnfs layouts) using one MDS and one DS. I have
> a client that mount pNFS volume.
>
> I can touch (create) files on that volume immediately:
> time touch c
>
> real 0m0.005s
> user 0m0.000s
> sys 0m0.000s
>
> But creating files with a content suffers from approx. 15 secs timeout:
>
> dd if=/dev/zero of=testf10 bs=1M count=1
> 1+0 records in
> 1+0 records out
> 1048576 bytes (1.0 MB) copied, 15.1156 s, 69.4 kB/s
>
> overwriting the same file works OK:
>
> dd if=/dev/zero of=testf10 bs=1M count=1
> 1+0 records in
> 1+0 records out
> 1048576 bytes (1.0 MB) copied, 0.0258294 s, 40.6 MB/s
>
> I think this is an interesting part of the debug logs:
> [69615.791232] pnfs_writeback_done: Begin (status -10008)
I'm not sure if that explains the 15 seconds delay.
I wonder if it could be related to the nfsv4 grace period.
Does this happen if you wait for a couple minutes after
the server restarts before starting the test?
Benny
> [69615.791238] put_lseg: lseg ffff88003b987840 ref 7 valid 1
> [69615.794450] NFS: 6195 nfs_writeback_done (status -10008 count 8192)
> [69615.794450] pnfs4_write_done DS write
> [69615.794450] nfs41_sequence_done: Error 0 free the slot
> [69615.794450] nfs4_free_slot: free_slotid 0 highest_used_slotid 5
> [69615.794450] <-- pnfs4_write_done status= -11
> [69615.990137] filelayout_write_call_done new off 8192 orig offset 8192
>
> Any ideas?
>
next prev parent reply other threads:[~2010-06-14 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:51 pNFS timeouts Lukas Hejtmanek
2010-06-14 14:11 ` Benny Halevy [this message]
2010-06-14 14:23 ` Lukas Hejtmanek
2010-06-14 14:46 ` Benny Halevy
2010-06-14 15:02 ` Benny Halevy
2010-06-14 15:12 ` Lukas Hejtmanek
2010-06-14 15:05 ` Lukas Hejtmanek
2010-06-14 15:10 ` Benny Halevy
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=4C163892.20201@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/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