From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Benny Halevy <bhalevy@panasas.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, Andy Adamson <andros@netapp.com>
Subject: Re: pNFS timeouts
Date: Mon, 14 Jun 2010 17:12:31 +0200 [thread overview]
Message-ID: <20100614151231.GF17703@ics.muni.cz> (raw)
In-Reply-To: <4C164490.6010903@panasas.com>
On Mon, Jun 14, 2010 at 11:02:40AM -0400, Benny Halevy wrote:
> looking at http://charon.styxx.cz/tmp/pnfs/pnfs_write_log.txt
> There seem to 15 seconds form after getting an NFS4ERR_DELAY
> from a DS write to the respective commit.
this debug is not applicable to DS?
echo 32767 > /proc/sys/sunrpc/nfs_debug
I can provide debug output from DS, but this does not seem to produce a=
ny
debug output.
--=20
Luk=E1=B9 Hejtm=E1nek
next prev parent reply other threads:[~2010-06-14 15:12 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
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 [this message]
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=20100614151231.GF17703@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=andros@netapp.com \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--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