Valentin has 2 PRs up to address this on the snapd/core20 side:
https://github.com/snapcore/snapd/pull/9 and
https://github.com/snapcore/core20/pull/124
** Changed in: snapd
Assignee: (unassigned) => Valentin David (valentin.david)
** Changed in: snapd
Status: Confirmed => In
> 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
I continue to see these messages on all UC20 VM's I use, including the
most recently released stable image on cdimage when booted in a VM
** Changed in: snapd
Status: Expired => Confirmed
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification
[Expired for snapd because there has been no activity for 60 days.]
** Changed in: snapd
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920107
Title:
Failed
IMO it is out of scope for finalrd to unmount mounts which can't be
cleanly unmounted.
** Changed in: finalrd (Ubuntu)
Status: Incomplete => Opinion
** Changed in: finalrd (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920107
Title:
Failed messages of sd-umount shown with reboot/shutdown
To manage
** Description changed:
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:
I also can reproduce this issue in my amd64 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920107
Title:
Failed messages of sd-umount shown with reboot/shutdown
To manage notifications
@Dimitri,
The issue can be reproduced by http://cdimage.ubuntu.com/ubuntu-
core/20/stable/current/ubuntu-core-20-amd64.img.xz while I previously
fetched the image there to test, so if you think it's snap relevant, I
can check with snapd team.
--
You received this bug notification because you
The way uc20 is booted, and how bind mounts are setup means that we do
force unmount eventually.
It matters which snaps are installed, and which processes have memory
mapped which files.
Many things should probably be marked for lazyunmount.
Please provide details why is held up
** Summary changed:
- Failed messages of sd-umoun show with reboot/shutdown
+ Failed messages of sd-umount shown with reboot/shutdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920107
Title:
11 matches
Mail list logo
