xfs
[Top] [All Lists]

Re: xfs_db 2.9.8: coredump

To: Eric Sandeen <sandeen@xxxxxxxxxx>
Subject: Re: xfs_db 2.9.8: coredump
From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Fri, 26 Dec 2008 12:52:10 -0500 (EST)
Cc: xfs@xxxxxxxxxxx, esandeen@xxxxxxxxxx, Alan Piszcz <ap@xxxxxxxxxxxxx>
In-reply-to: <alpine.DEB.1.10.0812261243550.18703@xxxxxxxxxxxxxxxx>
References: <alpine.DEB.1.10.0812260931490.11656@xxxxxxxxxxxxxxxx> <49551073.5090704@xxxxxxxxxx> <alpine.DEB.1.10.0812261243550.18703@xxxxxxxxxxxxxxxx>
User-agent: Alpine 1.10 (DEB 962 2008-03-14)


On Fri, 26 Dec 2008, Justin Piszcz wrote:



On Fri, 26 Dec 2008, Eric Sandeen wrote:

Justin Piszcz wrote:
# xfs_db -V
xfs_db version 2.9.8

p34:~# xfs_db -c frag -f /dev/sda1
Segmentation fault (core dumped)
p34:~# xfs_db -c frag -r /dev/sda1
Segmentation fault (core dumped)

(It was working BEFORE I ran xfs_fsr on it, it was at 16% fragmentation).

Now it can no longer check it?


Or, get an xfs_metadump of the fs and see if db segfaults on that too.

I'd be curious  to know if xfs_repair -n flaggs any problems, as well.

-Eric


p34:~# umount /r1
p34:~# sync
p34:~# xfs_db -c frag -r /dev/sda1
actual 365758, ideal 358711, fragmentation factor 1.93%
p34:~# mount -a
p34:~# xfs_db -c frag -r /dev/sda1
actual 365758, ideal 358711, fragmentation factor 1.93%
p34:~# mount -a ; dmesg | tail -n 2
p34:~# xfs_fsr /dev/sda1
/r1 start inode=0
p34:~# xfs_db -c frag -r /dev/sda1
actual 365751, ideal 358711, fragmentation factor 1.92%
p34:~#

Now it is working?  I do not understand.

<Prev in Thread] Current Thread [Next in Thread>