Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_repair\s+segfaults\s+with\s+ag_stride\s+option\s*$/: 10 ]

Total 10 documents matching your query.

1. xfs_repair segfaults with ag_stride option (score: 1)
Author: Tom Crane <T.Crane@xxxxxxxxxx>
Date: Wed, 1 Feb 2012 13:36:12 +0000
Dear XFS Support, I am attempting to use xfs_repair to fix a damaged FS but always get a segfault if and only if -o ag_stride is specified. I have tried ag_stride=2,8,16 & 32. The FS is approx 60T. I
/archives/xfs/2012-02/msg00005.html (18,815 bytes)

2. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 2 Feb 2012 07:42:49 -0500
Hi Tom, Thanks for the detailed bug report. Can you please try the attached patch? Attachment: repair-fix-dirbuf Description: Text document
/archives/xfs/2012-02/msg00039.html (8,094 bytes)

3. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Tom Crane <T.Crane@xxxxxxxxxx>
Date: Mon, 06 Feb 2012 00:50:59 +0000
Hi Christoph, Many thanks for the quick response and the patch. It was a big help. I was able to repair our 60TB FS in about 30 hours. I have a couple of questions; (1) The steps in the progress repo
/archives/xfs/2012-02/msg00127.html (49,398 bytes)

4. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sun, 05 Feb 2012 23:58:24 -0600
Newer tools are fine to use on older filesystems, there should be no issue there. running fsr can cause an awful lot of IO, and a lot of file reorganization. (meaning, they will get moved to new loca
/archives/xfs/2012-02/msg00130.html (10,710 bytes)

5. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Tom Crane <T.Crane@xxxxxxxxxx>
Date: Mon, 6 Feb 2012 11:19:07 +0000
Eric Sandeen wrote: On 2/5/12 6:50 PM, Tom Crane wrote: Hi Christoph, Many thanks for the quick response and the patch. It was a big help. I was able to repair our 60TB FS in about 30 hours. I have a
/archives/xfs/2012-02/msg00138.html (12,260 bytes)

6. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 06 Feb 2012 07:21:32 -0600
... which does: answer = (double)(extcount_actual - extcount_ideal) * 100.0 / (double)extcount_actual; If you work it out, if every file was split into only 2 extents, you'd have "50%" - and really,
/archives/xfs/2012-02/msg00144.html (11,827 bytes)

7. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 6 Feb 2012 09:04:29 -0500
Do you mean the out of order agno progress reports? That's an artefact of the ag_stride option which parallelizes processing of different AGs, and expected. It's not very nice but I don't have a smar
/archives/xfs/2012-02/msg00145.html (8,694 bytes)

8. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Tom Crane <T.Crane@xxxxxxxxxx>
Date: Tue, 07 Feb 2012 17:41:10 +0000
Eric Sandeen wrote: On 2/6/12 5:19 AM, Tom Crane wrote: Eric Sandeen wrote: ... Newer tools are fine to use on older filesystems, there should be no Good! issue there. running fsr can cause an awful
/archives/xfs/2012-02/msg00179.html (17,542 bytes)

9. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 07 Feb 2012 12:00:20 -0600
ok, so that's a fair number of extents, although I don't know how big the file is. I think "Frag" takes into account sparseness, so that doesn't account for it. (i.e. frag on a sparse file w/ 5 fille
/archives/xfs/2012-02/msg00181.html (14,682 bytes)

10. Re: xfs_repair segfaults with ag_stride option (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 8 Feb 2012 20:00:41 +1100
..... Ok, so that looks like you have a fragmentation problem here. What is the workload that is generating these files? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
/archives/xfs/2012-02/msg00209.html (11,141 bytes)


This search system is powered by Namazu