Red Hat Bugzilla – Bug 225155
Unexpected ext/XFS corruption
Last modified: 2007-11-30 17:11:54 EST
Description of problem:
XFS gets corrupted right at the first run from harddisk. (Yes, I know XFS is not
supported, but really, right after the initial install?) Can be fixed up with
xfs_repair, but files get damaged when not fixed up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install FC6 in textmode, with xfs (linux text xfs)
2. deselect all install components but Administrative Tools
Not die on me right away.
It seems that the filesystem was not cleanly unmounted after the install from
CD, because fsck.xfs gave a warning, and the rpm database was bust.
Created attachment 146831 [details]
Something similar happens to ext3. Though it's limited to the time-problem.
(XFS got both the time issue and corruption.)
The XFS issue was fixed up in the first update after release I think.
for xfs, this is probably a dup of bug #212201 but I would need some actual
information to know for sure (xfs_repair output maybe? fsck.xfs is a no-op, not
Are things any better if you boot w/ selinux=0 and do not enable selinux on the
If it is the xfs selinux/attr problem, Dave has a patch to fix this but it's not
available in an update yet...
you've mentioned corruption on both ext3 and xfs, but haven't offered any info
to show me how it's corrupted, so it'll be hard to move forward on this.
Created attachment 147863 [details]
Screenshot of XFS errors
That block number looks well out of range. Does xfs_repair find anything? And,
do you have selinux enabled on this box, or are you using extended attributes
via beagle, or other application?
In lieu of other info, assuming this is the attr2 bug that plagued early F6, and
it's fixed now. If you can show otherwise, please re-open.