From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: 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 11:10:49 -0600 [thread overview]
Message-ID: <49551019.7030802@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0812260931490.11656@p34.internal.lan>
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?
>
> ===============================================================================
>
> Program terminated with signal 11, Segmentation fault.
> [New process 11346]
> (gdb) bt
> #0 0x00007f6a67c8c3e0 in ?? () from /lib/libc.so.6
> #1 0x00007f6a67c8b43a in memmove () from /lib/libc.so.6
> #2 0x0000000000403f2e in ?? ()
> #3 0x0000000000412ff1 in ?? ()
> #4 0x00000000004129cb in ?? ()
> #5 0x0000000000413392 in ?? ()
please run against a debug binary so we can get useful info...
If this was on fedora, just install the matching xfsprogs-debuginfo package.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-26 18:06 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 [this message]
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
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=49551019.7030802@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ap@solarrain.com \
--cc=esandeen@redhat.com \
--cc=jpiszcz@lucidpixels.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