Re: [Qemu-devel] Massive read only kvm guests when backing file was missing

From: Alejandro Comisario
Date: Tue Apr 01 2014 - 10:10:12 EST


The conclusion is that the backing file stored on NFS that is the same
for all 950 hosts / 10500 guests was deleted and immediatelly raised a
read-only filesystem on the guest, seems that there's no way to avoid
that.

We developed a script to recover from that scenario if the same happens.
Basically doing:

* virsh stop
* qemu-ndb connect
* fsck
* qemu-ndb disconnect
* virsh start

best regards.


Alejandro Comisario
MercadoLibre Cloud Services
Arias 3751, Piso 7 (C1430CRG)
Ciudad de Buenos Aires - Argentina
Cel: +549(11) 15-3770-1857
Tel : +54(11) 4640-8443


On Tue, Apr 1, 2014 at 10:52 AM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote:
> On Mon, Mar 31, 2014 at 09:51:23PM -0300, Alejandro Comisario wrote:
>> Again, thanks to everyone.
>
> Did you reach a conclusion or is there still a problem that might be a
> bug in KVM?
>
> Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/