Bug 237893
| Summary: | Busy inodes after unmount oops with nfs4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Don Howard <dhoward> |
| Component: | kernel | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Martin Jenner <mjenner> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | dzickus, pawsa, rgautier, staubach, steved |
| 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: | 2008-05-22 18:26:50 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
Don Howard
2007-04-25 21:47:48 UTC
Hmm with no reliable reproducer, this might be tough to track down. I'll have a look over the oops and see what we might be able to determine from it (but I fear that the answer there is "not much"). Yes, it's a tough one to reproduce. Factors that tend to correlate with it are nfs4, autofs (use short timeout to remount the file system often) and, I get impression, several user accessing the same filesystem (like in: first one user triggers the mount, next, another one). I have seen "Busy inodes" with 2.6.18-8.1.8 too, although it has clearly become more difficult to trigger. Its been quite a while since this has been seen, so I'm going to close this as INSUFFICIENT_DATA. If this oops happens again, please reopen... |