| To: | Richard Ems <richard.ems@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Segmentation fault in xfs_db frag, xfsprogs-3.1.8 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 06 Jun 2012 09:57:25 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4FCF2BAC.6050100@xxxxxxxxxxxxxxxxx> |
| References: | <4FCC77E1.4030600@xxxxxxxxxxxxxxxxx> <20120605234528.GD22848@dastard> <4FCF2BAC.6050100@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Still seeing hangs in xlog_grant_log_space, Brian Foster |
|---|---|
| Next by Date: | Re: Still seeing hangs in xlog_grant_log_space, Chris J Arges |
| Previous by Thread: | Re: Segmentation fault in xfs_db frag, xfsprogs-3.1.8, Dave Chinner |
| Next by Thread: | [PATCH v2] xfs: Fix overallocation in xfs_buf_allocate_memory(), Jan Kara |
| Indexes: | [Date] [Thread] [Top] [All Lists] |