All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 44731] ext4 deadlock under heavy io?
Date: Mon, 16 Jul 2012 20:54:14 +0000 (UTC)	[thread overview]
Message-ID: <20120716205414.B3E7511FB37@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-44731-13602@https.bugzilla.kernel.org/>

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





--- Comment #2 from Anssi Hannula <anssi.hannula@iki.fi>  2012-07-16 20:54:14 ---
Created an attachment (id=75501)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=75501)
sysrq-w output on 3.4.2 with frozen filesystem dm-4

I'm seeing a very similar issue on 3.4.2. I think this issue didn't exist
several major versions back.

When one or more applications do intensive I/O, the filesystem freezes and all
processes trying to access it freeze as well.

It doesn't always happen in the same way, though. Sometimes I get the "task
blocked for more than 120 seconds", but sometimes I don't (in the attached case
I didn't get those). Also, sometimes the system becomes usable again after
several minutes of being seemingly frozen, but often it doesn't recover (like
in the attached case). If wanted, I can provide more logs of these different
situations (the logs do look very similar than the ones on this report,
though).

In the attachment the frozen fs is dm-4. It is on the same LVM VG and RAID-6 as
dm-3, dm-5, dm-6, and those other filesystems continued to work while dm-4 was
frozen.

-- 
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-07-16 20:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 12:23 [Bug 44731] New: ext4 deadlock under heavy io? bugzilla-daemon
2012-07-13 14:01 ` [Bug 44731] " bugzilla-daemon
2012-07-13 14:06 ` bugzilla-daemon
2012-07-16 20:54 ` bugzilla-daemon [this message]
2012-08-29 14:23 ` bugzilla-daemon
2012-08-29 15:09 ` bugzilla-daemon
2012-08-29 15:50 ` bugzilla-daemon
2012-08-29 16:07 ` bugzilla-daemon
2012-08-29 16:12 ` bugzilla-daemon
2012-08-29 16:38 ` bugzilla-daemon
2012-08-29 17:26 ` bugzilla-daemon
2012-08-30  8:18 ` bugzilla-daemon
2012-08-30  9:06 ` bugzilla-daemon
2012-08-30  9:41 ` bugzilla-daemon
2012-08-30 13:34 ` bugzilla-daemon
2012-08-31  9:23 ` bugzilla-daemon
2012-08-31 13:03 ` bugzilla-daemon
2012-09-03 10:24 ` bugzilla-daemon
2012-10-24 20:38 ` bugzilla-daemon
2013-11-20  0:04 ` 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=20120716205414.B3E7511FB37@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.