Bug 206870 - xfsprogs prior to 2.8.10 have a really serious bug
Summary: xfsprogs prior to 2.8.10 have a really serious bug
Keywords:
Status: CLOSED DUPLICATE of bug 206869
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-utils
Version: 5
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-17 13:25 UTC by Valent Turkovic
Modified: 2015-01-04 22:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-17 13:29:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Valent Turkovic 2006-09-17 13:25:19 UTC
Description of problem:
I know that you officially doesn't support anything but ext3 but you still put 
xfsprogs package with fedora and there is a really big problem with it.

xfsprogs prior to 2.8.10 have a really serious bug which leads to xfs partition 
errors and xfs_repair can't repair the errorous partition.

xfs partition crashes, gives read and write errors and running xfs_repair 
doesn't repair it. 

The bug is described in here:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=631

You need to put an updated xfsprogs 2.8.10 or newer package for fedora core 5, 
and all other.

Thank you.

Version-Release number of selected component (if applicable):
xfs 2.6, fedora core 5

How reproducible:
just work with files on xfs partition, and soon they break

Steps to Reproduce:
1.
2.
3.
  
Actual results:
fatal error -- can't read block 16777216 for directory inode 23727780

Expected results:
xfs_repair should repair all errors on xfs partition

Additional info:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=631
http://www.http://tinyurl.com/h4o9h
http://tinyurl.com/fhs29

Comment 1 Johan Kok 2006-09-17 13:29:48 UTC
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

*** This bug has been marked as a duplicate of 206869 ***


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