From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 44731] ext4 deadlock under heavy io?
Date: Fri, 13 Jul 2012 14:06:40 +0000 (UTC) [thread overview]
Message-ID: <20120713140640.313E311FAD0@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-44731-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=44731
Mirek Rusin <mirek@me.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mirek@me.com
--- Comment #1 from Mirek Rusin <mirek@me.com> 2012-07-13 14:06:39 ---
Some additional information:
- this hang situation happens very rarely, I'd say maybe every 10TBytes of data
written (at 1Gbit/sec).
- there are maximum of 32 threads doing io.
- each io operation is at most 0.5MB of data (written or read) per syscall with
an exception of fallocate, which can be rarely large, ie. 60GB.
- this situation happens on both empty volumes (where fallocate can find
continuous blocks to do any requested fallocate) and, what seems more often,
when disk is close to being full.
- the volume is LSI RAID6 with 500MB cache and 24x 2TB hard drives
- i'm able to do several hundred of ios per second normally, the hang seems to
be caused by the kernel itself and not hardware
- during the hang i can access and write to the volume from other
processes/threads.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-07-13 14:06 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 [this message]
2012-07-16 20:54 ` bugzilla-daemon
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=20120713140640.313E311FAD0@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.