You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a multi disk btrfs volume as root fs for the vm.
Each disk needs to grow on first boot and the btrfs filesystem should be resized.
Partitions are grown just fine and btrfs detects that, however, running btrfs filesystem resize max / as currently used in
This bug was originally filed in Launchpad as LP: #1955858
Launchpad details
Launchpad user Richard Schwab(nothing4you) wrote on 2021-12-28T01:05:59.703006+00:00
cloud provider: self-hosted, proxmox
cloud-init config:
growpart:
mode: auto
devices:
- /dev/sda1
- /dev/sdb1
- /dev/sdc1
- /dev/sdd1
I have a multi disk btrfs volume as root fs for the vm.
Each disk needs to grow on first boot and the btrfs filesystem should be resized.
Partitions are grown just fine and btrfs detects that, however, running
btrfs filesystem resize max /
as currently used incloud-init/cloudinit/config/cc_resizefs.py
Line 81 in bae9b11
From the
btrfs-filesystem
man page (debian 11, Btrfs v5.10.1):Since a devid is not passed only the first disk will be resized, other disks will stay with "slack" space.
This is after I manually resized disk id 2 for testing, before it also had 3GiB slack:
root@test-vm:~# btrfs device usage /
/dev/sda1, ID: 1
Device size: 4.00GiB
Device slack: 3.50KiB
Data,RAID10: 310.25MiB
Metadata,RAID10: 64.00MiB
System,RAID10: 8.00MiB
Unallocated: 3.62GiB
/dev/sdb1, ID: 2
Device size: 4.00GiB
Device slack: 3.50KiB
Data,RAID10: 310.25MiB
Metadata,RAID10: 64.00MiB
System,RAID10: 8.00MiB
Unallocated: 3.62GiB
/dev/sdc1, ID: 3
Device size: 4.00GiB
Device slack: 3.00GiB
Data,RAID10: 310.25MiB
Metadata,RAID10: 64.00MiB
System,RAID10: 8.00MiB
Unallocated: 640.73MiB
/dev/sdd1, ID: 4
Device size: 4.00GiB
Device slack: 3.00GiB
Data,RAID10: 310.25MiB
Metadata,RAID10: 64.00MiB
System,RAID10: 8.00MiB
Unallocated: 640.73MiB
The text was updated successfully, but these errors were encountered: