Bug 79842
Summary: | (FS VFAT)Strange error (Stale NFS file handle) using VFAT partition | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dusan Djordjevic <dj.dule> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | alan, eddie.kuns, emile, scotto |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-05-21 20:10:08 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
Dusan Djordjevic
2002-12-17 13:38:20 UTC
I have also seen this. I did not see this problem with RH8.0 and the original kernel version. I started seeing this issue only after running up2date and getting later Red Hat kernel releases for 8.0. Additional note -- this is probably the same bug as in Bugzilla entry 83779 *** Bug 83779 has been marked as a duplicate of this bug. *** I'm seeing this bug on redhat 9.0 too while accessing a FAT32 partition created with mkfs.vfat VFAT doesnt have stable inode numbering that is needed for NFS. If you were paying attention, you would see that this has nothing to do with NFS. The FAT32 partitions in question are not being NFS served or received. NFS may or may not even be running on the machines in question. That is why this is a bug and why this is a strange error. I suspect that later kernel updates to 9.0 may have fixed this as I haven't seen it again. But if I do see it again I will open a new bug and point out the fact that on my machine where I saw this I DO NOT HAVE NFS RUNNING. Yup, same here. I have this problem and I don't have NFS running. Yes I missed that. ESTALE can only occur over NFS ... at least in theory. Practice seems to be bizarrely different here fs/namei.c: link_path_walk(), d->op->d_revalidate fails. vfat_revalidate checks the dentry->d_time matches the version of the parent. The mv moved the parent but seems not to have invalidated the dentry in any way. vfat_rename fails to change dentry->d_time or drop the dentry. In bug, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83779 which is marked as a duplicate of this one, there was no mv command. Could this one and that one have the same root problem anyway? I think so. Testing a fix Closing - works in Fedora Core 2 |