http://bugzilla.opensuse.org/show_bug.cgi?id=1084213 Bug ID: 1084213 Summary: [libstorage-ng][Leap 15 + SLE 15 suspected] /home subvolume not created if user opts to not have a /home partition Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: rbrown@suse.com QA Contact: jsrain@suse.com CC: dimstar@opensuse.org, kukuk@suse.com, okurz@suse.com Found By: --- Blocker: --- Created attachment 762888 --> http://bugzilla.opensuse.org/attachment.cgi?id=762888&action=edit y2logs Steps to reproduce: - Install any libstorage-ng OS on a blank disk - Choose guided setup during partitioning - Select Disk - Leave LVM and Disk Encryption unticked (as default) - On the settings for the Root Partition Screen - configure the following: - UNTICK Propose Separate Home Partition - Leave all the other boxes as default (File System type BTRFS, Snapshots enabled, Separate Swap enabled, Enlarge RAM for Suspend) The resulting proposal has only 8 subvolume actions creating the following subvolumes @ @/var @/usr/local @/tmp @/srv @/opt @/boot/grub2/x86_64 @/boot/grub2/i386-pc @/home is missing, this is unexpected and crates a system with a critical flaw. There is the potential for serious data loss for any user who installs their system showing this behaviour. That includes any fresh Tumbleweed installation from current snapshots, and potentially SLE-15 and Leap-15 assuming they are showing the same behaviour. Any user using rollbacks on these systems will loose all data in /home written since their last snapshot As we have no way of repairing subvolumes retroactively, any user who has installed any *SUSE OS that exhibits this behaviour will need to *RE-INSTALL* to recover from this bug. It's essential that when using btrfs as the rootfs without /home as a separate partition, the @/home subvolume is created. This is the purpose of the associated lines in the control.xml, which seem to be ignored at the moment: https://github.com/yast/skelcd-control-openSUSE/blob/master/control/control.... y2logs attached These logs are from an installation in topped immediately after proposal is presented; my other system struck by this bug is currently inaccessible, on account of it bring remote, only allowing ssh key authentication, and as it's ssh keys were held in /home, they were lost during a rollback. (okurz, ccing you to this bug because I am concerned about the SLE-15 impact, can you or someone from QA take a look?) -- You are receiving this mail because: You are on the CC list for the bug.