Ubuntu
xfsprogs package

xfs_repair fails to repair filesystem

Bug #1189567 reported by RoyK
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfsprogs (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Won't Fix
Medium
Unassigned
Quantal
Won't Fix
Medium
Unassigned
Raring
Fix Released
Undecided
Unassigned
Saucy
Fix Released
Undecided
Unassigned

Bug Description

xfs_repair finds errors, but fails to repair the filesystem. This is apparently fixed in xfsprogs 3.1.8 according to sandeen on #xfs @ irc.freenode.net. See http://karlsbakk.net/tmp/xfs_metadump.log.1.gz for the metadump.

roy

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xfsprogs 3.1.7
ProcVersionSignature: Ubuntu 3.8.0-23.34~precise1-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Mon Jun 10 19:43:38 2013
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm-color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xfsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
RoyK (roysk) wrote :
Revision history for this message
RoyK (roysk) wrote :

This output is repeated after each xfs_repair http://paste.ubuntu.com/5752403/

Revision history for this message
RoyK (roysk) wrote :

Also, since this is about a filesystem used in production, I think it should get pretty high priority.

Revision history for this message
RoyK (roysk) wrote :

<sandeen> on #xfs @ irc.freenode.net, apparently working for redhat, confirmed this bug on xfsprogs 3.1.7, but not on 3.1.1 or 3.1.8.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Raring & saucy have 3.1.9. If you want this particular bug to be fixed in Quantal/Precise. Please follow https://wiki.ubuntu.com/StableReleaseUpdates and update the bug description to include impact, steps to reproduce. Then you or somebody else needs to cherry-pick patches to fix just this issue & upload SRUs for this bug.

Changed in xfsprogs (Ubuntu Saucy):
status: New → Fix Released
Changed in xfsprogs (Ubuntu Raring):
status: New → Fix Released
Changed in xfsprogs (Ubuntu Quantal):
status: New → Incomplete
Changed in xfsprogs (Ubuntu Precise):
status: New → Incomplete
Changed in xfsprogs (Ubuntu Quantal):
importance: Undecided → Medium
Changed in xfsprogs (Ubuntu Precise):
importance: Undecided → Medium
Revision history for this message
RoyK (roysk) wrote :

Well, I'm just a sysadmin. I was hoping someone at Ubuntu/Canonical would know more about the guts in xfsprogs than I do. Aren't there anyone responsible for this package? It's in the main repo, and should be officially supported. I find it somewhat strange to ask the reporter (me) to come up with the patch. This was fixed, along with "Numerous xfs_repair fixes" (from the source) in 3.1.8. And, btw, not being able to repair a damaged filesystem should probably allow this bug to be prioritised a *bit* more than "medium".

roy

Revision history for this message
RoyK (roysk) wrote :

I've linked to the metadump, and wit hthis, it's no problem reproducing the error. Pelease change the status from Incomplete, andd please upgrade its priority. This bug inhibits repairing a filesystem, which is a bad thing indeed.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Rolf Leggewie (r0lf)
Changed in xfsprogs (Ubuntu Quantal):
status: Incomplete → Won't Fix
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in xfsprogs (Ubuntu Precise):
status: Incomplete → Won't Fix
Revision history for this message
RoyK (roysk) wrote :

In case anyone's interested - this problem was solved by replacing a bad power supply. The disks were given too low voltage and didn't appreciate that, failing all over.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.