From: Ken Moffat <zarniwhoop@ntlworld.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3}
Date: Tue, 19 Jun 2012 00:38:02 +0100 [thread overview]
Message-ID: <20120618233802.GA20382@milliways> (raw)
In-Reply-To: <1340050299.20570.4.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
On Mon, Jun 18, 2012 at 08:11:40PM +0000, Myklebust, Trond wrote:
>
> 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.
>
I'm attaching the bzip2'd output from the trigger [ 151k before
compressing ] - I guess that the lines from 1346 (the backup script)
onwards, and particularly from 1417 (rsync in state D) are the parts
of most interest. The last line is because I killed the backup with
Ctrl-C.
For the debug: I assume /proc/sys/sunrpc/rpc_debug is the thing ?
It didn't seem to do anything (udev-181) - but I only looked at the
log, forgot to look at dmesg.
I've also got an nfs_debug file there. Tried echoing 0 to that,
reran the backup script but it now ends normally and there is still
nothing in dmesg.
Created a short text file in /boot, backup ran normally. Added
another kernel image, used 'rpcdebug -s -m rpc all' and the same for
nfs, this time it hung. I suspect it isn't the rsync itself which
hangs, but updating or touching or deleting a status file. Might be
totally wrong there. Also, 0 in the debug file seems to turn it off.
I've grepped the separate NFS and RPC messages into nfs-only.bz2
and rpc-only.bz2.
Back to bisection.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
[-- Attachment #2: trigger.bz2 --]
[-- Type: application/octet-stream, Size: 14336 bytes --]
next prev parent reply other threads:[~2012-06-18 23:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 20:07 nfs3 problem with -rc{2,3} 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
2012-06-18 23:38 ` Ken Moffat [this message]
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=20120618233802.GA20382@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@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