Bug#888222: systemd: invalid mount order of btrfs subvolumes after apt upgrade and reboot

[Michael Biebl]

Hi

On Tue, 23 Jan 2018 19:39:29 -0500 "LeJacq, Jean Pierre"
<jeanpierre.lejacq at quoininc.com> wrote:
> Package: systemd
> Version: 236-3~bpo9+1
> Severity: normal
> 
> Dear Maintainer,
> 
> I have configured a btrfs based storage system with the followin
> characteristics:
> 
> * SSD drive using Opal Full Disk Encryption. No issues here.
> * UEFI/GPT drive with boot, swap, and btrfs partition.
> * btrfs configured with root subvolume and other volumes mounted over
>   this subvolume.
> * btrfs quota support enabled.
> * subvolume using secure mounting option. For example, /usr mounted
>   ro.
> 
> This configuration boots successfully with no errors
> reported. Hibernation works well.
> 
> The problem comes only after a system update.
> 
> * What led up to the situation?
> 
> I first remount /usr to rw. I update the system using apt upgrade. I
> then halt the system. Using a rescue system, I examine the btrfs
> subvolumes and no files exist in the mount point directories, so the
> shutdown seems to be fine.
> 
> I then reboot into the system. systemd seems to not properly wait for
> /tmp, /var, /var/log, /var/log/audit to be mounted before starting
> services that write into the mount point directories. systemd then
> reports a dependency error because of existing files in the mount
> point (message is not clear).
> 
> * What exactly did you do (or not do) that was effective (or
>   ineffective)?
> 
> I'm able to restore the system by booting into a rescue system, manual
> mount the btrfs subvolumes, and removing the files in the mount point
> directories. I then reboot into the system. It sometimes requires
> several attempts doing this - it's not clear why.
> 
> * What was the outcome of this action?
> 
> System works fine after this. Rebooting works without issue. The issue
> reoccurs 100% of the time after upgrading the system.
> 
> 
> * What outcome did you expect instead?
> 
> Upgrading the system should not cause mount dependency errors.
> 
> 
> I'll attach the journalctl output after a failed reboot.
> 
> 
> -- System information: partition information
> 
> $ sudo parted --list /dev/sda3 


Could you try with the latest version from stretch-backports and report
back if the issue is still reproducible.

Thanks,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181116/795e6857/attachment-0002.sig>