Red Hat Bugzilla – Bug 893904
xfs_repair segfaults when using ag_stride option.
Last modified: 2013-11-21 16:19:21 EST
Description of problem:
When running xfs_repair with the ag_stride option to attempt to speed up the repair, part way through Phase 2, we receive a segfault.
Version-Release number of selected component (if applicable):
[root@zeus ~]# rpm -qa | grep xfs
Steps to Reproduce:
[root@zeus ~]# xfs_repair -o bhash=16384 -o ihash=16384 -o ag_stride=16 -t 60 /dev/xvdb
Phase 1 - find and verify superblock...
- reporting progress in intervals of 1 minute
Phase 2 - using internal log
- zero log...
XFS: totally zeroed log
The latest version of xfsprogs (3.1.8) are known to fix this problem.
Updating xfsprogs would probably fix a whole lot of issues, as well as increase performance of actual repairs.
Author: Christoph Hellwig <email@example.com>
Date: Fri Mar 2 08:35:08 2012 +0000
repair: fix incorrect use of thread local data in dir and attr code
The attribute and dirv1 code use pthread thread local data incorrectly in
a few places, which will make them fail in horrible ways when using the
Replace the use of thread local data with simple local allocations given
that there is no needed to micro-optimize these allocations as much
as e.g. the extent map. The added benefit is that we have to allocate
less memory, and can free it quickly.
Reviewed-by: Dave Chinner <firstname.lastname@example.org>
Reported-by: Tom Crane <T.Crane@rhul.ac.uk>
Tested-by: Tom Crane <T.Crane@rhul.ac.uk>
Signed-off-by: Christoph Hellwig <email@example.com>
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.