(One intermediate revision by the same user not shown)
Line 2:
Line 2:
Because a complete balance may take '''a long time''', there is the possibility of filters in balance. When using a filter only those chunks will be balanced, that are named by the filter.
Because a complete balance may take '''a long time''', there is the possibility of filters in balance. When using a filter only those chunks will be balanced, that are named by the filter.
* '''balance''' all chunks that are less than 50% full. This '''will''' take some time !
* '''balance''' all chunks that are less than 50% full. This '''will''' take some time !
{{BoxWarning|Don't use filters higher than 90%|This is unnecessary on an SSD drive. On a hard drive, this will put a lot of strain on the disk. Even with today's hard drives (>2TB), it may take a very long time. (e.g. 24 hours or more)}}
{{BoxWarning|Don't use filters higher than 95%|This is unnecessary on an SSD drive. On a hard drive, this will put a lot of strain on the disk. Even with today's hard drives (>2TB), it may take a very long time. (e.g. 24 hours or more)}}
Latest revision as of 10:17, 22 July 2025
Filters
Because a complete balance may take a long time, there is the possibility of filters in balance. When using a filter only those chunks will be balanced, that are named by the filter.
balance all chunks that are less than 50% full. This will take some time !
root # btrfs balance start -dusage=50 / COPY TO CLIPBOARD
balance all chunks that are less than 90% full. This will take some time !
root # btrfs balance start -dusage=90 / COPY TO CLIPBOARD
Don't use filters higher than 95%This is unnecessary on an SSD drive. On a hard drive, this will put a lot of strain on the disk. Even with today's hard drives (>2TB), it may take a very long time. (e.g. 24 hours or more)