* xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
@ 2007-05-29 18:05 Justin Piszcz
2007-05-30 0:41 ` David Chinner
2007-05-30 2:41 ` Eric Sandeen
0 siblings, 2 replies; 6+ messages in thread
From: Justin Piszcz @ 2007-05-29 18:05 UTC (permalink / raw)
To: xfs; +Cc: apiszcz
# 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%
#
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
2007-05-29 18:05 xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume Justin Piszcz
@ 2007-05-30 0:41 ` David Chinner
2007-05-30 2:25 ` Chris Wedgwood
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 2:41 ` Eric Sandeen
1 sibling, 2 replies; 6+ messages in thread
From: David Chinner @ 2007-05-30 0:41 UTC (permalink / raw)
To: Justin Piszcz; +Cc: xfs, apiszcz
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
2007-05-30 0:41 ` David Chinner
@ 2007-05-30 2:25 ` Chris Wedgwood
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 8:45 ` Justin Piszcz
1 sibling, 1 reply; 6+ messages in thread
From: Chris Wedgwood @ 2007-05-30 2:25 UTC (permalink / raw)
To: David Chinner; +Cc: Justin Piszcz, xfs, apiszcz
On Wed, May 30, 2007 at 10:41:40AM +1000, David Chinner wrote:
> Remember - xfs_fsr does best effort defrag - if it can't make
> progress, it does nothing, and it can't defrag directories...
Also, it's not going to do much in many cases unless you have free
space... if you don't have enough *suitable* free space then it won't
be able to do much.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
2007-05-30 2:25 ` Chris Wedgwood
@ 2007-05-30 8:45 ` Justin Piszcz
0 siblings, 0 replies; 6+ messages in thread
From: Justin Piszcz @ 2007-05-30 8:45 UTC (permalink / raw)
To: Chris Wedgwood; +Cc: David Chinner, xfs, apiszcz
On Tue, 29 May 2007, Chris Wedgwood wrote:
> On Wed, May 30, 2007 at 10:41:40AM +1000, David Chinner wrote:
>
>> Remember - xfs_fsr does best effort defrag - if it can't make
>> progress, it does nothing, and it can't defrag directories...
>
> Also, it's not going to do much in many cases unless you have free
> space... if you don't have enough *suitable* free space then it won't
> be able to do much.
>
Currently have 101GB used with 645GB free.
Justin.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
2007-05-30 0:41 ` David Chinner
2007-05-30 2:25 ` Chris Wedgwood
@ 2007-05-30 8:45 ` Justin Piszcz
1 sibling, 0 replies; 6+ messages in thread
From: Justin Piszcz @ 2007-05-30 8:45 UTC (permalink / raw)
To: David Chinner; +Cc: xfs, apiszcz
On Wed, 30 May 2007, David Chinner wrote:
> 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
>
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 746G 101G 645G 14% /d2
# xfs_db -c "frag -v" -f /dev/md1
inode 512 actual 0 ideal 0
inode 513 actual 0 ideal 0
inode 514 actual 0 ideal 0
inode 515 actual 3 ideal 1
inode 518 actual 0 ideal 0
inode 146353073 actual 0 ideal 0
inode 146353075 actual 3 ideal 1
inode 146353076 actual 1 ideal 1
..
inode 4160750217 actual 1 ideal 1
inode 4160750218 actual 1 ideal 1
inode 4160750219 actual 1 ideal 1
# xfs_db -c "frag -v" -f /dev/md1 | wc
422
Thoughts?
# xfs_db -c "inode 146353073" -c bmap -f /dev/md1
# (no output)
# xfs_db -c "inode 4160750219" -c bmap -f /dev/md1
data offset 0 startblock 260410208 (31/363360) count 740 flag 0
Justin.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume
2007-05-29 18:05 xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume Justin Piszcz
2007-05-30 0:41 ` David Chinner
@ 2007-05-30 2:41 ` Eric Sandeen
1 sibling, 0 replies; 6+ messages in thread
From: Eric Sandeen @ 2007-05-30 2:41 UTC (permalink / raw)
To: Justin Piszcz; +Cc: xfs, apiszcz
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%
> #
So you have on average 1.114 extents per file.
Relax. Have a homebrew. :)
-Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-05-30 8:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-29 18:05 xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume Justin Piszcz
2007-05-30 0:41 ` David Chinner
2007-05-30 2:25 ` Chris Wedgwood
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 8:45 ` Justin Piszcz
2007-05-30 2:41 ` Eric Sandeen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox