From: Boaz Harrosh <bharrosh@panasas.com>
To: Dick Streefland <dick.streefland@altium.nl>
Cc: <rnews@altium.nl>, <linux-nfs@vger.kernel.org>
Subject: Re: NFSv3 client hang on many simultanious reads
Date: Thu, 23 Aug 2012 13:45:19 +0300 [thread overview]
Message-ID: <503609BF.60809@panasas.com> (raw)
In-Reply-To: <4d25.5034e746.eefd1@altium.nl>
On 08/22/2012 05:05 PM, Dick Streefland wrote:
<>
>
> The client kernel version is 3.4.7, but the problem also exists in 3.1
> kernels. I cannot reproduce lockups with a 3.0 kernel. The server is
> running Linux 3.1.4. The mount options from /proc/mounts are:
>
It seems from above that the problem was introduced between 3.0
and 3.1.
Would it be at all possible for you to do a "git bisect" between
3.0 and 3.1 to Identify the bad commit that introduced this problem?
Thanks in advance
Boaz
next prev parent reply other threads:[~2012-08-23 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 14:05 NFSv3 client hang on many simultanious reads Dick Streefland, rnews
2012-08-23 10:45 ` Boaz Harrosh [this message]
2012-08-23 20:04 ` Dick Streefland, rnews
2012-08-29 12:11 ` Dick Streefland, rnews
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=503609BF.60809@panasas.com \
--to=bharrosh@panasas.com \
--cc=dick.streefland@altium.nl \
--cc=linux-nfs@vger.kernel.org \
--cc=rnews@altium.nl \
/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).