[xfs-masters] [Bug 986] New: xfs_repair segfault in get_inode_offset

bugzilla-daemon at oss.sgi.com bugzilla-daemon at oss.sgi.com
Wed Aug 21 11:38:46 CDT 2013


http://oss.sgi.com/bugzilla/show_bug.cgi?id=986

            Bug ID: 986
           Summary: xfs_repair segfault in get_inode_offset
           Product: XFS
           Version: Current
          Hardware: All
                OS: Linux
            Status: RESOLVED
          Severity: major
          Priority: P5
         Component: xfsprogs
          Assignee: xfs-masters at oss.sgi.com
          Reporter: fastcat at gmail.com
    Classification: Unclassified
            Status: RESOLVED
        Resolution: FIXED

I have an XFS filesystem that xfs_repair cannot fix, it segfaults every time. 
I've tested with 3.1.8-3.1.11 inclusive, and the current git head.

Attached are (all generated using xfsprogs git head):

sdc2_xfsrepair.anon.log: output of xfs_repair attempting to repair the
filesystem, with file and directory names anonymized.

sdc2_metadump.gz: xfs_metadump output for the filesystem

sdc2_metadump.log: warnings generated by xfs_metadump for above

gdb.log: backtrace of the segfault in xfs_repair

--- Comment #1 from Matthew Gabeler-Lee <fastcat at gmail.com> ---
Created attachment 311
  --> http://oss.sgi.com/bugzilla/attachment.cgi?id=311&action=edit
xfs_repair output, anonymized

--- Comment #2 from Matthew Gabeler-Lee <fastcat at gmail.com> ---
Created attachment 312
  --> http://oss.sgi.com/bugzilla/attachment.cgi?id=312&action=edit
xfs_metadump output

--- Comment #3 from Matthew Gabeler-Lee <fastcat at gmail.com> ---
Created attachment 313
  --> http://oss.sgi.com/bugzilla/attachment.cgi?id=313&action=edit
warnings generated by xfs_metadump

--- Comment #4 from Matthew Gabeler-Lee <fastcat at gmail.com> ---
Created attachment 314
  --> http://oss.sgi.com/bugzilla/attachment.cgi?id=314&action=edit
backtrace of segfault

--- Comment #5 from Matthew Gabeler-Lee <fastcat at gmail.com> ---
One of the commits between the original git head I tested (205267) and the
current (3ac87f) appears to have fixed this.  The log message for the current
head sounds like the error seen, and testing against the parent commit (0340d7)
still shows the error.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs-masters/attachments/20130821/e7189671/attachment-0001.html>


More information about the xfs-masters mailing list