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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMrG31zp5Sq4j7O+1AsaVNLpyc2QpfRU5FEFDmS7hyOSELS50Q@mail.gmail.com>
Date:	Tue, 1 Apr 2014 11:09:37 -0300
From:	Alejandro Comisario <alejandro.comisario@...cadolibre.com>
To:	Stefan Hajnoczi <stefanha@...il.com>
Cc:	Michael Tokarev <mjt@....msk.ru>, qemu-devel@...gnu.org,
	kvm@...r.kernel.org, "Michael S. Tsirkin" <mst@...hat.com>,
	ghammer@...hat.com, Jason Wang <jasowang@...hat.com>,
	linux-kernel@...r.kernel.org, Markus Armbruster <armbru@...hat.com>
Subject: Re: [Qemu-devel] Massive read only kvm guests when backing file was missing

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@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/