All of lore.kernel.org
 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: Fri,  1 Jun 2012 16:26:59 +0000 (UTC)	[thread overview]
Message-ID: <20120601162659.F3DB611FD1B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43292-13602@https.bugzilla.kernel.org/>

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





--- Comment #16 from Jan Kara <jack@suse.cz>  2012-06-01 16:26:59 ---
Grumble, it's the same, just for a different allocation group:
253,2    0     6514    25.375884394   744  Q   R 707526656 + 8 [nfsd]
  9,0    0     5451    25.375887257   744  A   R 749576576 + 8 <- (253,2)
707526
656
  9,0    0     5452    25.375888584   744  Q   R 749576576 + 8 [nfsd]
  8,16   0    17311    25.375891308   744  A   R 749576639 + 8 <- (8,17)
7495765
76
  8,16   0    17312    25.375892077   744  Q   R 749576639 + 8 [nfsd]
  8,16   0    17313    25.375894381   744  G   R 749576639 + 8 [nfsd]
  8,16   0    17314    25.375895918   744  P   N [nfsd]
  8,16   0    17315    25.375898572   744  I   R 749576639 + 8 [nfsd]
  8,16   0    17316    25.375900038   744  U   N [nfsd] 1
  8,16   0    17317    25.375901715   744  D   R 749576639 + 8 [nfsd]

Let's try the following:
for (( i = 0; i < 25293; i++ )); do
  dd if=/dev/dm-2 of=/dev/null bs=4k count=1 skip=$(($i*32768))
done

Again run it before and after the hang. If it finishes even after the hang,
check whether nfsd is still hung.

-- 
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-06-01 16:27 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
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 [this message]
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=20120601162659.F3DB611FD1B@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.