On the one hand, fsr is probably safe, although it doesn't get a whole
lot of testing* because...
...on the other hand, it's rarely needed. In fact, XFS existed for a
few years without this tool. Because of the way XFS allocates space on
disk, fragmentation is kept at a minimum.
You can check fragmentation on an unmounted filesystem:
[root@stout root]# xfs_db /dev/sda1
xfs_db: frag
actual 2204, ideal 2196, fragmentation factor 0.36%
See man xfs_db for more info...
-Eric
*QA 042 does exercise xfs_fsr a bit, though:
# XFS QA Test No. 042
# $Id: 042,v 1.2 2000/09/27 00:24:22 ajag Exp ajag $
#
# xfs_fsr QA tests
# create a large fragmented file and check that xfs_fsr doesn't corrupt
# it or the other contents of the filesystem
On Tue, 2001-12-04 at 08:35, Walt H wrote:
> Hello all,
>
> I've been using xfs for nearly one year on one of my linux boxes, and
> after some minor glitches early on, all is working well. Great work! My
> question concerns xfs_fsr. Is it safe to use? Will I see any benefit if
> I set it up to run as a cron job maybe twice a week? I read through the
> man page and it sounds like something I should be doing for regular
> maintenance, I'm just a bit timid about reorganizing a mounted
> filesystem. The particular system I'm talking of is an Athlon XP 2.4.16
> kernel compiled with kgcc running 2 IBM GXP60 40GB striped. Thanks in
> advance.
>
> -Walt
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|