From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
Alan Piszcz <ap@solarrain.com>,
xfs@oss.sgi.com
Subject: Re: xfs_db 2.9.8: coredump
Date: Sun, 28 Dec 2008 22:48:39 -0600 [thread overview]
Message-ID: <495856A7.6040608@sandeen.net> (raw)
In-Reply-To: <20081228223917.GC22525@disturbed>
Dave Chinner wrote:
> On Fri, Dec 26, 2008 at 12:52:10PM -0500, Justin Piszcz wrote:
>> 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?
>
> xfs_db works on the block device under the filesystem, not the
> filesystem. Also, the block device on linux caches blocks, so
> after running xfs_fsr the filesystem layout has changed but the
> underlying block device now has a stale cache. hence xfs_db is
> probably being pointed off into la-la land by the stale block
> device cache.
Ah, missed the part about doing it online. Probably shouldn't segfault
though, I suppose.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-29 4:49 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 [this message]
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=495856A7.6040608@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ap@solarrain.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