From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Alan Piszcz <ap@solarrain.com>,
esandeen@redhat.com, xfs@oss.sgi.com
Subject: Re: xfs_db 2.9.8: coredump
Date: Fri, 26 Dec 2008 13:18:37 -0600 [thread overview]
Message-ID: <49552E0D.1030809@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0812261243550.18703@p34.internal.lan>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-26 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 14:36 xfs_db 2.9.8: coredump Justin Piszcz
2008-12-26 17:10 ` Eric Sandeen
2008-12-26 17:12 ` Eric Sandeen
2008-12-26 17:45 ` Justin Piszcz
2008-12-26 17:52 ` Justin Piszcz
2008-12-28 22:39 ` Dave Chinner
2008-12-28 22:44 ` Justin Piszcz
2008-12-29 4:48 ` Eric Sandeen
2008-12-26 19:18 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49552E0D.1030809@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ap@solarrain.com \
--cc=esandeen@redhat.com \
--cc=jpiszcz@lucidpixels.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox