Bug 477942
Summary: | fsck clears orphan inodes instead of linking into lost+found | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | G.Wolfe Woodbury <redwolfe> |
Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10 | CC: | esandeen, kzak, oliver |
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-12-27 17:58:40 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
G.Wolfe Woodbury
2008-12-26 03:33:19 UTC
please provide a log of the fsck run so I can see exactly what it is doing. Thanks, -Eric There are no logs *per se* since they take place during the system bootup process. One can, fairly easly (but dangerously) reproduce the problem by powering down the system without shutting down first. basically, the autofsck reports that orphan inodes are found (typically in /usr filesystem) and report that they have been cleared. They are *not* zero-lenght files, but they are cleared instead of linked to lost+found. I've seen this F8 and have been wondering why we bother with lost+found at all if the systems isn't going to use it! Orphan inodes *should* be cleared; these were files that were unlinked while they were open, and then a crash happened. Deleting them on the next boot is exactly what should happen, it completes the unlinking that would have happened when the last user closed the file post-unlink. Also, lost+found is not a junkbox for corrupted inodes, it is specifically for inodes which have lost their parent link. If fsck doesn't find such inodes, it won't populate lost+found. This is why I asked for the details of the fsck run, I need to see what it's doing and why to determine if it's doing anything wrong. But if they are truly orphan inodes then clearing them is exactly right. I'm going to NOTABUG this, based on your description of what is happening. Thanks, -Eric Just to be sure, was it something like: Clearing orphan inode 12345 (uid=XXX, gid=XXX, mode=XXX, size=XXX) ? |