xfs
[Top] [All Lists]

Re: xfs_db 2.9.8: coredump

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: xfs_db 2.9.8: coredump
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 26 Dec 2008 13:18:37 -0600
Cc: Eric Sandeen <sandeen@xxxxxxxxxx>, Alan Piszcz <ap@xxxxxxxxxxxxx>, esandeen@xxxxxxxxxx, xfs@xxxxxxxxxxx
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: Thunderbird 2.0.0.18 (Macintosh/20081105)
Justin Piszcz wrote:
> 
> On Fri, 26 Dec 2008, Eric Sandeen wrote:


>> 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
>>
> 
> # xfs_metadump -g /dev/sda1  /root/sda1.metadump
> Copied 300096 of 426176 inodes (0 of 12 AGs)
> Copying log
> #
> 
> p34:~# xfs_db -c frag -f sda1.metadump
> xfs_db: unexpected XFS SB magic number 0x5846534d
> xfs_db: read failed: Invalid argument
> xfs_db: data size check failed
> cache_node_purge: refcount was 1, not zero (node=0x1ce4b80)
> xfs_db: cannot read root inode (22)
> cache_node_purge: refcount was 1, not zero (node=0x1ce4cd0)
> xfs_db: cannot read realtime bitmap inode (22)
> Segmentation fault (core dumped)

well, you have to xfs_mdrestore that to a sparse file before pointing db
at it for it to be valid (still, should not dump).

-Eric

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