[Bug 1920107] Re: Failed messages of sd-umount shown with reboot/shutdown

[Steve Langasek]

> IMO it is out of scope for finalrd to unmount mounts
> which can't be cleanly unmounted.

Er, this is nonsense. The entire point of finalrd is to ensure we pivot
to an initramfs after all other processes have been terminated, so that
it is possible to cleanly unmount the root filesystem with no errors.
For the root filesystem to be busy and failing to unmount is clearly a
bug in either systemd or finalrd.

** Changed in: finalrd (Ubuntu)
       Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to finalrd in Ubuntu.
https://bugs.launchpad.net/bugs/1920107

Title:
  Failed messages of sd-umount shown with reboot/shutdown

Status in snapd:
  Confirmed
Status in finalrd package in Ubuntu:
  Confirmed

Bug description:
  We were seeing the same sequence of errors heppened on KVM and ARM
  device running UC20:

  """
  [12450.684692] sd-umoun[5922]: Failed to unmount /oldroot: Device or resource busy
  [12450.693515] sd-remou[5923]: Failed to remount '/oldroot/run/mnt/data' read-only: Device or resource busy
  [12450.704374] sd-umoun[5924]: Failed to unmount /oldroot/run/mnt/data: Device or resource busy
  [12450.714225] sd-umoun[5925]: Failed to unmount /oldroot/run: Device or resource busy
  [12450.726073] shutdown[1]: Could not detach loopback /dev/loop0: Device or resource busy
  [12450.735481] shutdown[1]: Failed to finalize file systems, loop devices, ignoring
  [12451.129165] reboot: Power down
  """

  [Steps to reproduce]

  $ sudo poweroff or $ sudo reboot

  [Additional info]

  http://cdimage.ubuntu.com/ubuntu-core/20/stable/current/ubuntu-
  core-20-amd64.img.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1920107/+subscriptions