From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3}
Date: Mon, 18 Jun 2012 20:11:40 +0000 [thread overview]
Message-ID: <1340050299.20570.4.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20120618200525.GA15654@milliways>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1843 bytes --]
On Mon, 2012-06-18 at 21:05 +0100, Ken Moffat wrote:
> On Mon, Jun 18, 2012 at 05:00:05PM +0100, Ken Moffat wrote:
> > >
> > > OK. You said you had bisected this down to 15 patches? Can you please
> > > tell me which ones?
> > >
> >
> > I'm just about to resume, to see if I can get anywhere - the rc2
> > version built fine, so I'm guessing that some more of the remaining
> > versions will also build. Not sure which commits are still
> > outstanding.
> >
>
> Turned out that almost everything from 3e9e0ca3 failed to compile,
> until 4f97615d (fix for NFS_V4_1 undefined) resolved that, (only had
> one or two still to try when I decided to use 'git visualize'). And
> it was bad by 4f97615d.
>
> Added all the NFS v4 / 4.1 client options to my config :
> 3e9e0ca3 is now good, I'll start a fresh bisect between these two.
>
> Actually, I'd better retry 4f97515d to confirm it is still bad with
> this config. [ saves this message, tests ... ]. Rude words! If I
> enable all the NFS v4 client options, 4f97615d is good.
>
> Looks, to me, as if something in that untested range of patches, or
> in 3e9e0ca3 itself, causes the problem *if* nfs v4 is not enabled.
OK. That's helpful... I've been compiling a kernel without CONFIG_NFS_V4
enabled, and have run a few tests using fsx. So far, I haven't managed
to reproduce your issue.
The next time that you see the hang, can you try to run the command
'echo "t" >/proc/sysrq-trigger' as root?
If you can compile with CONFIG_SUNRPC_DEBUG, then an 'echo 0
>/proc/sys/rpc_debug' might also be helpful.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2012-06-18 20:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 20:07 Ken Moffat
2012-06-18 1:11 ` Ken Moffat
2012-06-18 13:42 ` Myklebust, Trond
2012-06-18 13:45 ` Myklebust, Trond
2012-06-18 14:18 ` Ken Moffat
2012-06-18 14:53 ` Myklebust, Trond
2012-06-18 16:00 ` Ken Moffat
2012-06-18 20:05 ` Ken Moffat
2012-06-18 20:11 ` Myklebust, Trond [this message]
2012-06-18 23:38 ` Ken Moffat
2012-06-18 23:44 ` Ken Moffat
2012-06-18 21:53 ` Ken Moffat
2012-06-18 22:03 ` Myklebust, Trond
2012-06-18 22:10 ` Ken Moffat
2012-06-19 1:06 ` nfs3 problem with -rc{2,3} : blame Ken Moffat
2012-06-19 16:20 ` Myklebust, Trond
2012-06-19 16:23 ` Myklebust, Trond
2012-06-19 16:55 ` Ken Moffat
2012-06-19 17:46 ` Myklebust, Trond
2012-06-19 19:35 ` Ken Moffat
2012-06-19 22:44 ` Myklebust, Trond
2012-06-19 23:31 ` Ken Moffat
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=1340050299.20570.4.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.com \
/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
all inboxes | Powered by JetHome®