From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42763] New: directory access hangs without error
Date: Mon, 13 Feb 2012 03:41:28 GMT [thread overview]
Message-ID: <bug-42763-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42763
Summary: directory access hangs without error
Product: File System
Version: 2.5
Kernel Version: 3.2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: ebuddington@wesleyan.edu
Regression: No
Kernel 3.2.5
ext4 over RAID-6
I have a specific directory that freezes all processes that try to getdents()
or open() a new file. In some cases, the kernel gives me "blocked for more
than 120 seconds" messages, often reporting that the process is stuck in
ext4_getblk.
I have found no errors, however. The stuck processes stay stuck forever (at
least hours), and dmesg shows no complaints about RAID, filesystem, or anything
else. Full reads of the RAID devices work without hanging, and drive self-tests
pass.
Other processes are able to access other parts of the filesystem normally; this
is not a system-wide or fs-wide hang.
Rebooting and fscking made the directory accessible again, but now there is a
different directory exhibiting the problem (unknown whether it had the problem
before the fsck/reboot)
This particular problem exhibited itself for the first time after tests of my
multi-threaded 'du' that beat the filesystem with a few dozen threads
simultaneously.
Given that this seems to very reproducible, I have many opportunities to poke
at a hung process, query the filesystem, or recompile the kernel in any way
that would be helpful; I just don't know to approach it from here.
--
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 reply other threads:[~2012-02-13 3:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 3:41 bugzilla-daemon [this message]
2012-02-13 15:55 ` [Bug 42763] directory access hangs without error bugzilla-daemon
2012-02-13 16:02 ` bugzilla-daemon
2012-02-13 16:56 ` bugzilla-daemon
2012-02-13 17:57 ` bugzilla-daemon
2012-02-13 18:21 ` bugzilla-daemon
2012-02-13 18:30 ` bugzilla-daemon
2012-02-14 14:22 ` Jan Kara
2012-02-17 5:33 ` Dave Chinner
2012-02-13 20:29 ` bugzilla-daemon
2012-02-14 5:07 ` bugzilla-daemon
2012-02-20 17:31 ` bugzilla-daemon
2012-02-20 17:32 ` bugzilla-daemon
2012-02-24 2:22 ` bugzilla-daemon
2012-08-30 14:35 ` 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=bug-42763-13602@https.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