Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_fsr\s+2\.2\.38\s+bug\/kernel\s+2\.6\.21\.3\s+cannot\s+defrag\s+volume\s*$/: 18 ]

Total 18 documents matching your query.

1. xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Tue, 29 May 2007 14:05:44 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449
/archives/xfs/2007-05/msg00303.html (7,781 bytes)

2. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 30 May 2007 10:41:40 +1000
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
/archives/xfs/2007-05/msg00304.html (8,972 bytes)

3. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Tue, 29 May 2007 19:25:24 -0700
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.
/archives/xfs/2007-05/msg00305.html (8,474 bytes)

4. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 29 May 2007 21:41:11 -0500
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00306.html (8,690 bytes)

5. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:16 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00308.html (10,363 bytes)

6. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:38 -0400 (EDT)
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
/archives/xfs/2007-05/msg00309.html (9,181 bytes)

7. xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Tue, 29 May 2007 14:05:44 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449
/archives/xfs/2007-05/msg00638.html (7,781 bytes)

8. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 30 May 2007 10:41:40 +1000
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
/archives/xfs/2007-05/msg00639.html (8,972 bytes)

9. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Tue, 29 May 2007 19:25:24 -0700
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.
/archives/xfs/2007-05/msg00640.html (8,474 bytes)

10. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 29 May 2007 21:41:11 -0500
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00641.html (8,690 bytes)

11. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:16 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00643.html (10,363 bytes)

12. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:38 -0400 (EDT)
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
/archives/xfs/2007-05/msg00644.html (9,181 bytes)

13. xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Tue, 29 May 2007 14:05:44 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449
/archives/xfs/2007-05/msg00973.html (7,775 bytes)

14. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 30 May 2007 10:41:40 +1000
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
/archives/xfs/2007-05/msg00974.html (9,052 bytes)

15. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Chris Wedgwood <cw@xxxxxxxx>
Date: Tue, 29 May 2007 19:25:24 -0700
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.
/archives/xfs/2007-05/msg00975.html (8,580 bytes)

16. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 29 May 2007 21:41:11 -0500
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00976.html (8,716 bytes)

17. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:16 -0400 (EDT)
Linux boxname 2.6.21.3 #2 SMP Sun May 27 11:34:21 EDT 2007 i686 GNU/Linux xfs_fsr version 2.2.38 xfs_db version 2.8.18 actual 449, ideal 403, fragmentation factor 10.24% /d2 start inode=0 actual 449,
/archives/xfs/2007-05/msg00978.html (10,153 bytes)

18. Re: xfs_fsr 2.2.38 bug/kernel 2.6.21.3 cannot defrag volume (score: 1)
Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Wed, 30 May 2007 04:45:38 -0400 (EDT)
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..
/archives/xfs/2007-05/msg00979.html (9,223 bytes)


This search system is powered by Namazu