On 12/10/2014 02:15 PM, sys.syphus wrote:
I am working on a script that i can run daily that will do maintenance
on my btrfs mountpoints. is there any reason not to concurrently do
all of the above? possibly including discards as well.
also, is there anything existing currently that will do maintenance on
btrfs so i don't have to reinvent the wheel?
#!/bin/bash
btrfs filesystem defragment -r -v /media/btrfs/ &
btrfs scrub start /media/btrfs/ &
btrfs balance start /media/btrfs/ &
watch -d -n 30 "btrfs balance status /media/btrfs/; btrfs scrub status
/media/btrfs/"
I'd recommend doing "none of the above" on a daily basis. One of the
goals of the filesystem design is to remove the need for any of these
operations on any regular basis. You are just going to bog down your
system and increase you heat and wear profiles for no good reason.
Those tools should be used if you notice something fishy like recent
decreases in efficiency or errors in your log files.
A _monthly_ scrub is maybe worth scheduling if you have a lot of churn
in your disk contents.
Defragging should be done after significant content additions/changes
(like replacing a lot of files via package management) and limited to
the directories most likely changed.
Balancing is almost never necessary and can be anti-helpful if a
experiences random updates in batches (because the nicely packed file
may end up far, far away from the active data extent where its COW
events are taking place.
Resist the urge to tinker with production systems. The exposure
(rewriting stable data is just the chance to destabilize your data,
balancing your drive can take two files that always change together and
put them far away from one another, etc) is not worth the nearly
non-existent chance of benefit. Once the system is "good" just leave it
that way until you notice something "not good" coming on the horizon.
If you feel you _must_ do these tasks then doing them all at once, where
possible, will just make both tasks take longer. If you are transcribing
a file over on one side of the disk to defrag it, and you are
transcribing an extent on the other side of the disk to balance it, you
are just bouncing your disk heads back-and-forth and wasing wall-clock time.
So yea, it's not windows, it doesn't need the defrag hammer.
Trying to over-manage the system will prevent it from seeking its
dynamic (and so predictable) equilibrium.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
