From: Dave Chinner <david@fromorbit.com>
To: Richard Ems <richard.ems@cape-horn-eng.com>
Cc: xfs@oss.sgi.com
Subject: Re: Segmentation fault in xfs_db frag, xfsprogs-3.1.8
Date: Wed, 6 Jun 2012 23:38:59 +1000 [thread overview]
Message-ID: <20120606133859.GM22848@dastard> (raw)
In-Reply-To: <4FCF2BAC.6050100@cape-horn-eng.com>
On Wed, Jun 06, 2012 at 12:06:36PM +0200, Richard Ems wrote:
> On 06/06/2012 01:45 AM, Dave Chinner wrote:
> > No surprise if you have a large filesystem and the filesystem is
> > changing while xfs_db is running. xfs_db is not coherent with
> > mounted filesytems, and it is not recommended that you use it that
> > way.s xfs-db is a debugging tool, not a filesystem state reporting
> > tool.
>
> Ok, thanks, didn't know that.
> I would like to monitor the fragmentation value for all my mounted XFS.
> I think I read in previous list messages that also other people are
> using xfs_db this way. Or is there another way to get the fragmentation
> value?
No, and what xfs_db reports is mostly useless. You don't have a
fragmentation problem unless you are noticing performance problems,
and no fragmentation number will ever tell you that....
> I found this segmentation fault error very strange, since I have been
> using "echo frag | xfs_db -r" for months already on other big
> filesystems - 2 x 17 TB, 1 x 25 TB, 1 x 20 TB - and NEVER got a
> segmentation fault. All 4 filessystems are mounted read-write and are in
> heavy IO use, nevertheless "echo frag | xfs_db -r" runs as expected (by
> me), no one xfs_db run crashed with a segmentation fault at all for
> months, running every weekend.
> It also ran several times without giving any errors on this 80 TB XFS,
> but then started to throw segmentation faults some weeks ago.
It's entirely possible it is running out of memory, failing to
capture the failure and dereferencing a null pointer....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-06 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:54 Segmentation fault in xfs_db frag, xfsprogs-3.1.8 Richard Ems
[not found] ` <20120605234528.GD22848@dastard>
2012-06-06 10:06 ` Richard Ems
2012-06-06 13:38 ` Dave Chinner [this message]
2012-06-06 14:57 ` 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=20120606133859.GM22848@dastard \
--to=david@fromorbit.com \
--cc=richard.ems@cape-horn-eng.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