From: Eric Sandeen <sandeen@sandeen.net>
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, 06 Jun 2012 09:57:25 -0500 [thread overview]
Message-ID: <4FCF6FD5.7020901@sandeen.net> (raw)
In-Reply-To: <4FCF2BAC.6050100@cape-horn-eng.com>
On 6/6/12 5:06 AM, 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?
As Dave said, this just isn't that useful.
http://xfs.org/index.php/XFS_FAQ#Q:_The_xfs_db_.22frag.22_command_says_I.27m_over_50.25.__Is_that_bad.3F
explains why.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-06-06 14:57 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
2012-06-06 14:57 ` 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=4FCF6FD5.7020901@sandeen.net \
--to=sandeen@sandeen.net \
--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