Closed calestyo closed 2 months ago
There are probably several things that could affect the shrink/grow increments. The minimum is one sectorsize, we had bugs where convert created a filesystem with non-sectorsize aligned size and then allocator complained. There's a round down step to make sure even such converted filesystems work. The same applies for resize. Another alignment is the stripe size that is hardcoded to 64K. The zoned mode uses that as the absolute minimum that would be a valid value for zone size or alignment.
The documentation update looks ok, so PR added to devel, but I guess it can be still improved. The rounding can be detected and at least mentioned when the btrfs
command is started, otherwise this is internal to the kernel iplementation and is not logged.
If you have further need for clarification please open a new issue as comments to PRs could get lost. Thanks.
Please review.
Further TODO:
resize max
, btrfs didn't claim that 512B. I’d blindly guess it's onesectorsize
as given bybtrfs inspect-internal dump-super
, what btrfs needs at least? If someone confirms I could make another commit that adds that information.