Bug 50516
Summary: | reiserfs umount hangs with Kernel 2.4.3-12 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Greg Folkert <gfolkert> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | http://www.namesys.com/download.html | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-01 15:07:17 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: |
Description
Greg Folkert
2001-07-31 19:50:19 UTC
Please try the 2.4.3-15 kernel at http://people.redhat.com/arjanv/testkernels/ it should have the fix for this. I installed kernel-2.4.3-15... No luck, still hangs. Currently made a new kernel(bzImage) with reiserfs in it (not a module), from source (2.4.7 from kernel.org), using config "kernel-2.4.3-i686.config" from 2.4.3-12 source. With the one change (a biggy I know) it now, works. It was the only way I can get it to NOT hang on umount, so far. This does not mean 2.4.7 is going to stay there, it is not default 2.4.3-15 is. Actual machine is: http://web.grcc.cc.mi.us Are you _very_ sure you were running -15 with the hang? The "common" hang on unmount was fixed in that, and several people reported success with it so far. You are correct, in assuming -12 was running. I archive configs as I go, yep My label said -15 but was running -12 (darn vi with yank and put, and me forgetting to edit the image line along with the label). My bad. When actually running the -15 Kernel, it does fix the problem. Although what intrigues me, is the 2.4.7 did the same as a module, but not as a compiled in component. Guess this is closed then. |