Skip to contentSkip to conversation

the 1st data chunk(8M) allocated by mkfs.btrfs can not be allocated again after full balance?

DISCUSSION Wang Yugui 2 participants 2 messages Aug 7, 2022 Btrfs file system

lore
Share & tools
lore

Wang Yugui

author
#0 lore raw

Hi,

The 1st data chunk allocated by mkfs.btrfs is 8M. After full balance, this 8M chunk is freed, and new allocated chunk size
is changed to 1G.

Then this 8M space can't be allocated again?
Or we should allocate 1G for 1st data chunk in mkfs.btrfs?

Best Regards
Wang Yugui ([email protected])
2022/08/07

#1 lore raw
Quoted 7 lines · Wang Yugui

Hi,

The 1st data chunk allocated by mkfs.btrfs is 8M. After full balance, this 8M chunk is freed, and new allocated chunk size
is changed to 1G.

Then this 8M space can't be allocated again?

It can, but needs very complex relcation, e.g. relocate all chunks to other devices (e.g. delete the device and add back).

Or run very low on unallocated space.

The reason why it can not be really utilized is, chunk allocator will always use the largest unallocated range by default.

Thus such small 8M will not be utilized until no more free space.

Quoted 1 line

Or we should allocate 1G for 1st data chunk in mkfs.btrfs?

I think we should follow kernel allocation size, but I'm not confident on small devices.

Thanks,
Qu

Quoted 5 lines

Best Regards
Wang Yugui ([email protected])
2022/08/07