In which cases does this happen? Should a vhost do high I/O at the time of
os-prober running to get fs corrupted?
Hi,
> update-grub on a vhost running qemu/kvm virtual machines
> while grub and os-prober is installed on the host might corrupt
> guest virtual machines / guest disks.
confirmed. This just tore Teckids' main infrastructure into pieces.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26
This bug seems to have put a few of my KVM Vm's into read-only.
Would it be possible to make the qemu-kvm package conflict with os-prober,
not allowing both packages to be installed simultaneous.
As I don't see a use case for os-prover of a KVM host.
Thanks for considering,
Barry de Graaff
Hi,
If this can't be fixed quickly, would it make sense to push an update
which disables os-prober on jessie in cases which are known to (even
possibly) lead to data loss?
I hate to post a "me too" message, but it's a little disheartening to
know that a bug that causes pretty bad data loss in
Unfortunately I must confirm this bug which is high critical!
My workaround was apt-get --purge remove os-prober
We can confirm this Bug (Debian 8.0 Jessie on VM host and guests).
os-prober version: 1.65 amd64
VM host
=
Sep 7 14:43:19 vm-host os-prober: debug: running
/usr/lib/os-probes/50mounted-tests on /dev/mapper/vm1-disk
Inside VM1
=
Sep 7 14:43:20 vm1 kernel: [4552906.712287]
The same behavior was observed for ext4 - if *any* superblock update
was made during os-prober execution, it could effectively corrupt a
filesystem in guest or, as for iSCSI, an exported one. The right
solution is to make a filesystem-specific checks like checking
EXT2_MF_BUSY before making an
I can confirm this, got the same problem with os-prober_1.63ubuntu1
Package: os-prober
Version: 1.65
Severity: critical
update-grub on a vhost running qemu/kvm virtual machines
while grub and os-prober is installed on the host might corrupt
guest virtual machines / guest disks.
Host
% lvs
LV VGAttr LSize
root
9 matches
Mail list logo
