| To: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Wed, 30 May 2007 10:41:40 +1000 |
| Cc: | xfs@xxxxxxxxxxx, apiszcz@xxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.64.0705291404430.2944@xxxxxxxxxxxxxxxx> |
| References: | <Pine.LNX.4.64.0705291404430.2944@xxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Tue, May 29, 2007 at 02:05:44PM -0400, Justin Piszcz wrote: > # uname -a > Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux > # xfs_fsr -V > xfs_fsr version 2.2.38 > # xfs_db -V > xfs_db version 2.8.18 > # xfs_db -c frag -f /dev/md1 > actual 449, ideal 403, fragmentation factor 10.24% > # xfs_fsr /dev/md1 > /d2 start inode=0 > # xfs_db -c frag -f /dev/md1 > actual 449, ideal 403, fragmentation factor 10.24% > # Try xfs_db -c "frag -v" -f /dev/md1 to see which inodes are fragmented, then run xfs_db -c "inode <num>" -c bmap -f /dev/md1 to see whether it is a sparse file or not.... Remember - xfs_fsr does best effort defrag - if it can't make progress, it does nothing, and it can't defrag directories... Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume, Justin Piszcz |
|---|---|
| Next by Date: | Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume, Chris Wedgwood |
| Previous by Thread: | xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume, Justin Piszcz |
| Next by Thread: | Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |