> And by the way, I just tested the old setup with your full
> recommendation, adding the BEFORE= statement and it finally stopped the
> I/O errors. I can now take the time to transition properly.
Awesome, glad I could help!
And it might help others who find this bug if affected by a similar
And by the way, I just tested the old setup with your full
recommendation, adding the BEFORE= statement and it finally stopped the
I/O errors. I can now take the time to transition properly.
Thank you!
Pedro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "systemd-analyze dot graph"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+attachment/5492912/+files/USRgraph.svg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Services, hook, and journal after adding AFTER= and
REQUIRES="
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+attachment/5492904/+files/buglog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Christian
I set this up back when without properly researching systemd.mount,
particularly the automatic dependencies. I make half of the changes you
recommended (Requires=virt-guest-shutdown.target; After=virt-guest-
shutdown.target) and it made no change, the I/O errors still showed up.
I'm
For your experiments, here a few examples
1. using a mount unit for ntfs
https://brunofontes.net/enu/post/mounting-partitions-systemd
2. doing disk setup with a service
Thanks,
In your log I see that stopping remote file systems and libvirtd
properly was ordered AFTER libvirt-guests tried to shut down the guest.
I've checked this in a few ways
1. libvirt/libvirt-guests vs remote fs (e.g. NFS)
2. libvirt/libvirt-guests vs NBD
#1 Remote-FS - well ordered
Apr
Hi Christian,
Thanks for your attention. I replicated the issue and here is the
journal log for today.
Regards
Pedro Serrano
On Wed, 2021-04-21 at 11:08 +, Christian Ehrhardt wrote:
> Hi Pedro,
>
> > Wouldn't it be beneficial for all guests to be shutdown before
> unmounting all
Sure can. I'm away but should have access to that laptop tomorrow
afternoon.
Would it matter if I re-created the conditions and sent you that
journal?
On Apr 21, 2021, 07:21, at 07:21, "Christian Ehrhardt "
<1924...@bugs.launchpad.net> wrote:
>Hi Pedro,
>
>> Wouldn't it be beneficial for all
Hi Pedro,
> Wouldn't it be beneficial for all guests to be shutdown before
unmounting all filesystems?
Yes on first sight that looks like a compelling suggestion.
But i've learned the hard way that usually adding dependencies eventually
breaks more things than it fixes - so let us first try to
** Package changed: systemd (Ubuntu) => libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924494
Title:
Systemd shutdown order unmounts filesystem used by qemu/kvm guest
before
11 matches
Mail list logo
