This started as debugging helper, to watch the effects of converting between raid levels on multiple devices, but could be useful standalone. In my case the usage filter was not finegrained enough and led to converting too many chunks at once. Another example use is in connection with drange+devid or vrange filters that allow to work with a specific chunk or even with a chunk on a given device. The limit filter applies last, the value of 0 means no limiting.
Showing the changes to include/uapi/linux (1 of 4 files). Show all
Unified · Split
| @@ -211,7 +211,8 @@ struct btrfs_balance_args { · 210 unmodified lines | ||
| 211 | 211 | |
| 212 | 212 | __u64 flags; |
| 213 | 213 | |
| 214 | − __u64 unused[8]; | |
| 214 | + __u64 limit; /* limit number of processed chunks */ | |
| 215 | + __u64 unused[7]; | |
| 215 | 216 | } __attribute__ ((__packed__)); |
| 216 | 217 | |
| 217 | 218 | /* report balance progress to userspace */ |