Bug 177122
| Summary: | VFS: busy inodes after unmount | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Aaron Straus <aaron> | ||||||
| Component: | kernel | Assignee: | Peter Staubach <staubach> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.0 | CC: | cfeist, ikent, jmoyer, steved | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2007-06-19 18:08:47 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 170416 | ||||||||
| Attachments: |
|
||||||||
|
Description
Aaron Straus
2006-01-06 15:13:50 UTC
Created attachment 122882 [details] fix one source of busy inodes after umount Do you have the means to port this patch to RHEL4 and give it a try? Also, if you are a Red Hat customer, please be sure to go through your TAM or https://enterprise.redhat.com/portal to ensure this gets the proper attention. Hi. We hit this again, this time on a RHEL4 ES machine. Same VFS message. Same oops. We are a redhat customer, well, we have enterprise subscriptions. I'm not sure that entitles us to the kind of support you are talking about? It doesn't look trivial to backport this patch. Thanks for your time. Please provide the information requested in the "Filing bug reports" section of my people page: http://people.redhat.com/jmoyer I understand that it takes a long time to reproduce, so you can skip the part about configuring debug logs. I do want to have a look at your maps, and I want to know which mountpoint disappeared just before the problem happened. Thanks! Created attachment 123677 [details]
Here is the information you requested.
This machine does NAT for some machines behind it which also use
autofs/ypbind/.. and are running similar jobs. Same exact setup, except they
are RHEL4 WS machines. One of them died very close to this time with the same
error. Others were ok. Thanks for your help.
OK. After looking at your maps, I don't think the attached patch will fix your problems. The reason is this: the patch addresses a case whereby unmounting an autofs file system may leave busy inodes. In your case, it is the act of unmounting an NFS file system that triggers the warning. It really looks to me as though this is an NFS issue. I'm going to reassign the bug to our NFS guru. I fully intended to put together a patch with some debugging information, but I don't know exactly what would be useful instrumentation at this point. Steve, could you please give this a look? Thanks. I forgot to change the component to kernel. Hi, I guess I'll re-open my original bug, since the duplicate bug fell silent. We finally were able to update our system to RH4-U4 WS. We saw the same trace again today. kernel was definitely 2.6.9-42.ELsmp. We might have to upgrade to U5 soon to fix an NFS cache bug we are also seeing, so we should be able to test the latest and greatest kernel in a week or so. If there is new information, please file a new bugzilla. This way, our recording keeping will keep straight. *** This bug has been marked as a duplicate of 173843 *** (In reply to comment #11) > If there is new information, please file a new bugzilla. This way, our > recording keeping will keep straight. > > *** This bug has been marked as a duplicate of 173843 *** Hi, I am reading through the description of 173843 and though the problem seems to manifest itself with the same symptoms, I'm not sure the cause is the same. In particular we are seeing this on NFS filesystems *only* with no GFS, ext3, ... involved. So I didn't want to re-open the 173843 bug as it seems that problem is fixed (or the submitter has gone quiet). Our problem is not fixed and might be a *separate* NFS problem. So re-opening this bug seems appropriate? Whatever you think is best, let me know. I have no new information to report other than it's still happening with the U4 kernel, which supposedly fixed the other bug (173843). Thanks! Looking through all the reports it looks like this might be closer to 177357. Though it's not clear what filesystem the reporter is seeing that bug on. I'll mark this as a duplicate of 177357, which still looks like an open issue. Thanks! *** This bug has been marked as a duplicate of 177357 *** |