Re: xfs_db on non-XFS FS causes a core dump (2.9.5-1)

["Barry Naujok" <bnaujok@xxxxxxx>]

On Fri, 22 Feb 2008 20:45:01 +1100, Justin Piszcz  
<jpiszcz@xxxxxxxxxxxxxxx> wrote:

> Should it core dump on this condition?

No it shouldn't. A fix for this is being worked on.

Barry.

> On Thu, 21 Feb 2008, Justin Piszcz wrote:
>
> > Checking fragmentation on a non-XFS filesystem causes xfs_db to core  
> > dump.
> >
> > # xfs_db -c frag -f /dev/sda
> > xfs_db: unexpected XFS SB magic number 0xfaeb2101
> > xfs_db: read failed: Invalid argument
> > xfs_db: data size check failed
> > cache_node_purge: refcount was 1, not zero (node=0x80dd670)
> > xfs_db: cannot read root inode (22)
> > cache_node_purge: refcount was 1, not zero (node=0x80dd770)
> > xfs_db: cannot read realtime bitmap inode (22)
> > Segmentation fault (core dumped)
> >
> > # dpkg -l | grep xfsprogs
> > ii  xfsprogs                             2.9.5-1
> >
> > Core was generated by `xfs_db -c frag -f /dev/sda'.
> > Program terminated with signal 11, Segmentation fault.
> > #0  0xb7ef3350 in pthread_mutex_lock () from /lib/libpthread.so.0
> > (gdb) bt
> > #0  0xb7ef3350 in pthread_mutex_lock () from /lib/libpthread.so.0
> > #1  0x080ab31a in ?? ()
> > #2  0x0000001c in ?? ()
> > #3  0x38006590 in ?? ()
> > #4  0x00000000 in ?? ()
> >
> > # xfs_db -c frag -f /dev/sda2
> > actual 208581, ideal 197229, fragmentation factor 5.44%