- 1. Segmentation fault during xfs_repair (score: 1)
- Author: Richard Kolkovich <richard@xxxxxxxxxxxxx>
- Date: Fri, 5 Jun 2009 17:22:37 -0500
- We have a corrupted XFS partition on a storage server. Attempting to run xfs_repair the first time yielded the message about a corrupt log file, so I have run xfs_repair with -L to clear that. Now, x
- /archives/xfs/2009-06/msg00084.html (8,835 bytes)
- 2. Re: Segmentation fault during xfs_repair (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Fri, 05 Jun 2009 21:45:37 -0500
- For starters, which xfsprogs version.... if not latest, try latest... if latest, I'll grab that metadump image and see if I can reproduce it. -Eric
- /archives/xfs/2009-06/msg00085.html (11,418 bytes)
- 3. Re: Segmentation fault during xfs_repair (score: 1)
- Author: Richard Kolkovich <richard@xxxxxxxxxxxxx>
- Date: Fri, 5 Jun 2009 22:14:46 -0500
- Sorry - forgot to mention that. Running on Fedora 11 (64bit). Tried using 2.10.2 (from yum) and building from latest stable source (3.0.1). Let me know if I should try a dev build. Thanks, -- Richard
- /archives/xfs/2009-06/msg00086.html (9,025 bytes)
- 4. Re: Segmentation fault during xfs_repair (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Fri, 05 Jun 2009 22:25:21 -0500
- (Hm, did I really leave F11 at 2.10.2? I thought it was newer, but anyway) No, I doubt anything else has fixed this since 3.0.1 I'll try pulling down that metadump image & see what I can see. Feel fr
- /archives/xfs/2009-06/msg00087.html (9,586 bytes)
- 5. Re: Segmentation fault during xfs_repair (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Fri, 05 Jun 2009 23:44:05 -0500
- ... Ok, on a -g (not -02) build: Program terminated with signal 11, Segmentation fault. da_cursor=0x7ffff4c4eb30, rbno=0x7ffff4c4ebdc) at dir2.c:356 356 da_cursor->level[i].hashval = (gdb) p i $1 = 4
- /archives/xfs/2009-06/msg00088.html (9,588 bytes)
- 6. Re: Segmentation fault during xfs_repair (score: 1)
- Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
- Date: Sat, 06 Jun 2009 00:10:12 -0500
- This should get you over that hump I think: -- xfsprogs-3.0.1.orig/repair/dir2.c 2009-06-06 00:01:10.711081870 -0500 +++ xfsprogs-3.0.1/repair/dir2.c 2009-06-06 00:05:52.993365954 -0500 @@ -353,6 +35
- /archives/xfs/2009-06/msg00089.html (8,353 bytes)
This search system is powered by
Namazu