Bug 129968
| Summary: | test kernel 2.6.8-1.520 makes umount to go into D state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2 | CC: | pfrields, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-11-28 08:29:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 102754 [details]
data collected via sysrq after umount got into D state
I meant, of course, "r/o remount via sysrq" and not "reboot". Sigh! mass update for old bugs: Is this still a problem with the 2.6.9 based update kernel ? > Is this still a problem with the 2.6.9 based update kernel ?
I do not think so. I did not see anything like that for a long time.
|
Description of problem: While remaking some initrd image the whole procedure ends in an unkillable umount like this: root 24885 0.0 0.0 41696 452 pts/0 D 17:39 0:00 \_ umount /tmp/initrd.mnt.o24736 This is part of ps output from some five minutes later after various failed attempts to dislodge the whole thing. Even with an emergency sync and r/o reboot via sysrq I ended up with a damage on /boot file system. Also attempts to shutdown orderly failed and I had to use sysrq "reboot" to get restore an order. A processor state and tasks from sysrq are attached; but it looks like this is an NFS code again even if I did not try to unmount an NFS mount. Version-Release number of selected component (if applicable): kernel-2.6.8-1.520 How reproducible: I would rather not try. :-)