Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225155 - Unexpected ext/XFS corruption
Summary: Unexpected ext/XFS corruption
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Eric Sandeen
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-29 14:47 UTC by Jan Engelhardt
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: f6 updates
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-09-17 19:07:34 UTC

Attachments (Terms of Use)
screenshot (deleted)
2007-01-29 15:13 UTC, Jan Engelhardt
no flags Details
Screenshot of XFS errors (deleted)
2007-02-11 19:56 UTC, Jan Engelhardt
no flags Details

Description Jan Engelhardt 2007-01-29 14:47:58 UTC
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):

How reproducible:

Steps to Reproduce:
1. install FC6 in textmode, with xfs (linux text xfs)
2. deselect all install components but Administrative Tools
Actual results:
Filesystem corruption.

Expected results:
Not die on me right away.

Additional info:
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.

Comment 1 Jan Engelhardt 2007-01-29 15:13:29 UTC
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.)

Comment 2 Dave Jones 2007-02-03 21:00:32 UTC
The XFS issue was fixed up in the first update after release I think.

Comment 3 Eric Sandeen 2007-02-04 00:47:01 UTC
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.


Comment 4 Jan Engelhardt 2007-02-11 19:56:56 UTC
Created attachment 147863 [details]
Screenshot of XFS errors

Comment 5 Eric Sandeen 2007-02-11 21:33:32 UTC
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?

Comment 6 Eric Sandeen 2007-09-17 19:07:34 UTC
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.



Note You need to log in before you can comment on or make changes to this bug.