linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 43292] jdb2 lockup with ext3 and nfs
Date: Thu, 31 May 2012 21:40:38 +0000 (UTC)	[thread overview]
Message-ID: <20120531214038.4714111FD1B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43292-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=43292





--- Comment #11 from Florian Pritz <flo@xssn.at>  2012-05-31 21:40:38 ---
Created an attachment (id=73480)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=73480)
output of dumpe2fs /dev/dm-2

(In reply to comment #10)
> I have to say I'm puzzled. Everything looks normal, the IO is submitted and
> completed, no sign of any hang. Just the last request - read - has been only
> submitted to disk and not yet completed but that can be just a coincidence. To
> check what has been read, can you attach here output of dumpe2fs /dev/dm-2?

I've run it without the hanging nfsd, is that correct?

> When the lockup happens, those nfsd threads are sitting there doing nothing for
> a long time, am I right?

Yeah. All nfs activity is frozen, but local system activity on the same file
system works just fine.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-05-31 21:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 15:54 [Bug 43292] New: jdb2 lockup with ext3 and nfs bugzilla-daemon
2012-05-26 20:31 ` [Bug 43292] " bugzilla-daemon
2012-05-29 14:04 ` bugzilla-daemon
2012-05-29 21:44 ` bugzilla-daemon
2012-05-30  9:18 ` bugzilla-daemon
2012-05-30  9:24 ` bugzilla-daemon
2012-05-30  9:41 ` bugzilla-daemon
2012-05-30  9:47 ` bugzilla-daemon
2012-05-30 13:33 ` bugzilla-daemon
2012-05-30 21:20 ` bugzilla-daemon
2012-05-31 20:16 ` bugzilla-daemon
2012-05-31 21:40 ` bugzilla-daemon [this message]
2012-05-31 22:44 ` bugzilla-daemon
2012-05-31 22:49 ` bugzilla-daemon
2012-06-01 15:24 ` bugzilla-daemon
2012-06-01 15:40 ` bugzilla-daemon
2012-06-01 16:26 ` bugzilla-daemon
2012-06-03 20:16 ` bugzilla-daemon
2012-06-04 10:19 ` bugzilla-daemon
2012-06-06 21:56 ` bugzilla-daemon
2012-06-07  9:29 ` bugzilla-daemon
2012-06-22 20:45 ` bugzilla-daemon
2012-06-27 13:49 ` bugzilla-daemon
2012-07-08 14:44 ` bugzilla-daemon
2012-07-10 13:12 ` bugzilla-daemon
2012-11-02 15:46 ` bugzilla-daemon

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=20120531214038.4714111FD1B@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).