** Changed in: lvm2 (Fedora)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system
Hi Yuri,
there was no recent change in regard to lvm handling in libvirt or lvm itself
that would obviously be related. Which Ubuntu release are you on - and between
which package versions did you upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This seems like a new problem to my after 6/24/20 update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system unmount
To
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1701234.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
It seems - somewhat expected - that the solution needs to be a bit
bigger due to further service dependencies that might create a loop.
Until that solution is sorted out upstream we should not implement
another custom emergency fix that might cause more trouble.
Instead while we wait on the final
Linked the related RH bug that was mentioned upstream
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Bug watch added: Red Hat Bugzilla #1701234
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Also affects: lvm2 (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Changed in: lvm2
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system unmount
To manage
Reported: https://github.com/lvmteam/lvm2/issues/18
Suggested: https://github.com/lvmteam/lvm2/pull/19
** Bug watch added: github.com/lvmteam/lvm2/issues #18
https://github.com/lvmteam/lvm2/issues/18
** Also affects: lvm2 via
https://github.com/lvmteam/lvm2/issues/18
Importance: Unknown
Thanks Erlend for the log.
I'm glad that the suggestion worked - now we need to check in which scope the
file is defined and ask for a change there - this should also ensure we are not
missing any hidden requirement that would be thwarted by that change (I could
think of it starting too late
I can confirm that adding Before=local-fs.target to blk-
availability.service solved the issue for me. Now everything happens in
the correct order. I attached the shutdown journal for reference.
** Attachment added: "shutdown.txt"
yeah I think I found the issue in your log.
Consider [1] again and look at
/lib/systemd/system/blk-availability.service
This is what calls blkdeactivate on shutdown.
It only has a
WantedBy=sysinit.target
But no ordering Before anything.
It even has
DefaultDependencies=no
which will make it
(I wrote the comment before realizing that I could only attach one file
. Journal.txt contains both shutdown and boot sequence.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during
Thank you for looking into this. I have attached the journal of one
shutdown and boot. It seems like during boot, everything happens in the
correct order. As you pointed out, this is as expected due to the
"After" parameter in the service-files.
However, as you can see from the shutdown.txt file,
I did some retries with bigger guests (slower) and such.
But all worked.
Attached an example of such a reboot cycle (main console).
You see shutdown waiting with FS unmount about 2 minutes for libvirt-guests
suspend.
Then on reboot it clearly is after FS mounts are up and therefore is able to
Repro:
$ sudo mkdir /var/test
$ echo "/var/test /var/lib/libvirt/qemu/save nonebind0 0" |
sudo tee -a /etc/fstab
$ sudo sed -i -e 's/#ON_SHUTDOWN=shutdown/ON_SHUTDOWN=suspend/'
/etc/default/libvirt-guests
$ sudo sed -i -e 's/#ON_BOOT=ignore/ON_BOOT=start/'
This is reported for issues with suspend and the example of
/var/lib/libvirt/qemu/save.
But IMHO this would be true for the more common case of guest shutdown (the
default) and /var being on an extra partition while the default image paths are
under /var.
I know this would not be an immediate
Requires would be wrong actually, there can be cases where these are not
strictly required.
But after should be fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown
Thanks for the report.
One might first think yeah lets add
Requires=local-fs.target
After=local-fs.target
But in fact it might need even more than that.
I wonder if (per [1]) the following might be even better.
Requires=sysinit.target
After=sysinit.target
Let me do some tests and maybe suggest
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system unmount
To manage notifications
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system unmount
To manage notifications
20 matches
Mail list logo
