http://bugzilla.suse.com/show_bug.cgi?id=1129566 http://bugzilla.suse.com/show_bug.cgi?id=1129566#c13 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Flags|needinfo?(ms@suse.com) | --- Comment #13 from Marcus Schaefer <ms@suse.com> --- I've setup an integration test based on your MicroOS description such that we have continuous testing of the feature set needed here. This image can be found here: https://build.opensuse.org/package/show/Virtualization:Appliances:Images:Tes... Based on that build I run a VM, and it comes up with the following layout: --- UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /.snapshots btrfs defaults,subvol=@/.snapshots 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /home btrfs defaults,subvol=@/home 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /opt btrfs defaults,subvol=@/opt 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /root btrfs defaults,subvol=@/root 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /srv btrfs defaults,subvol=@/srv 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /tmp btrfs defaults,subvol=@/tmp 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /usr/local btrfs defaults,subvol=@/usr/local 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /boot/grub2/i386-pc btrfs defaults,subvol=@/boot/grub2/i386-pc 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b /boot/grub2/x86_64-efi btrfs defaults,subvol=@/boot/grub2/x86_64-efi 0 0 UUID=c01309ae-ced9-4cb2-8eda-7711adab789b / btrfs ro 0 0 UUID=1b6dcaba-3bc3-457a-939b-ca2e3da38c38 /var ext4 defaults 0 0 UUID=06CC-D762 /boot/efi vfat defaults 0 0 ---
From a partition perspective it looks like this
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 24G 0 disk ├─sda1 8:1 0 2M 0 part ├─sda2 8:2 0 20M 0 part /boot/efi ├─sda3 8:3 0 19G 0 part / └─sda4 8:4 0 5G 0 part /var sr0 11:0 1 1024M 0 rom So /var is at the end and growable If you are looking for code that could grow the partition. I wrote this code for the public cloud. It is designed to grow root but it can easily be adapted to just grow whatever is last https://github.com/SUSE-Enceladus/rootgrow/pulls Does this provide the desired layout ? One question from my side. The system is read-only on /etc and other parts of the rootfs. I guess this is by intention ? Thanks -- You are receiving this mail because: You are on the CC list for the bug.