Bug 10242
Summary: | rm command hangs | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Jean-Luc Coulon (jean.luc.coulon) |
Component: | LVM2/DM | Assignee: | Alasdair G Kergon (agk) |
Status: | CLOSED CODE_FIX | ||
Severity: | high | CC: | bunk, rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25-rc5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 9832 | ||
Attachments: | task blocked, syslog for w to sysrq-trigger |
Description
Jean-Luc Coulon
2008-03-14 05:47:07 UTC
Does it only happen on luks volumes? try "echo w > /proc/sysrq-trigger" to see which tasks that are in uninterruptable (blocked) state. If possible, attach here. -Eric Created attachment 15267 [details]
task blocked, syslog for w to sysrq-trigger
I've never had the problem on non-luks volume. But non luks have poor write/delete activity (root filesystem, /usr)
I've had the problem no doing a rm but running a c++ compilation.
J-L
assume this is the known dm-crypt regression - we're working on a patch (a ref counting bug meaning in certain circumstances dm-crypt layer holds onto i/o for ever and never reports it completed) Is it a duplicate of Bug #10207? Most likely we won't know for sure whether it's the same as bug #10207 until there's a fix for which Jean-Luc can verify whether or not it fixes the problem for him? > Most likely we won't know for sure whether it's the same as bug #10207 until > there's a fix for which Jean-Luc can verify whether or not it fixes the > problem > for him? Please try patch in http://lkml.org/lkml/2008/3/14/347 I've tested the patch (on 2.6.25-rc5-git4). I've stressed a bit the system and I've no more the problem so far. Jean-Luc Latest patch for dm-crypt in http://lkml.org/lkml/2008/3/17/214 (the same patch mentioned in bug 10207) Please test the patch in comment 9 - I think that one's ready to submit. *** Bug 10207 has been marked as a duplicate of this bug. *** fixed by commit 3f1e9070f63b0eecadfa059959bf7c9dbe835962 |