From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:58494)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tiziano.mueller@stepping-stone.ch>)
	id 1TMb06-0003R7-Jr
	for qemu-devel@nongnu.org; Fri, 12 Oct 2012 04:53:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tiziano.mueller@stepping-stone.ch>)
	id 1TMb01-0007Hp-2D
	for qemu-devel@nongnu.org; Fri, 12 Oct 2012 04:53:46 -0400
Received: from mail.stepping-stone.ch ([194.176.109.206]:41058)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tiziano.mueller@stepping-stone.ch>)
	id 1TMb00-0007Hl-S2
	for qemu-devel@nongnu.org; Fri, 12 Oct 2012 04:53:40 -0400
Message-ID: <1350032011.4696.85.camel@storm>
From: Tiziano =?ISO-8859-1?Q?M=FCller?= <tiziano.mueller@stepping-stone.ch>
Date: Fri, 12 Oct 2012 10:53:31 +0200
In-Reply-To: <20121012082831.GA14822@stefanha-thinkpad.redhat.com>
References: <1349962403.4696.51.camel@storm>
	<20121012082831.GA14822@stefanha-thinkpad.redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Silent filesystem/qcow2 corruptions with
 qemu-kvm-1.0 and 1.1.1
Reply-To: tiziano.mueller@stepping-stone.ch
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

Am Freitag, den 12.10.2012, 10:28 +0200 schrieb Stefan Hajnoczi:
> On Thu, Oct 11, 2012 at 03:33:23PM +0200, Tiziano M=C3=BCller wrote:
> > One test case was:
> > * xfs_repair /dev/vda2 -> corruptions found and fixed
> > * xfs_repair /dev/vda2 -> no corruptions found
>=20
> From here...
>=20
> > * mount /dev/vda2 /mnt/something
> > * find /mnt/something > /dev/null
> > * umount /mnt/something
>=20
> ...to here is mostly read-only.
>=20
> > * xfs_repair /dev/vda2 -> corruptions found again
>=20
> And yet corruptions are reported inside the guest!
>=20
> Can you retry with "mount -o ro" just for sanity?  If you still see
> corruptions when the device was mounted read-only, then perhaps the
> mount/find/umount sequence itself is innocent.

Will try as soon as possible. The problem is that we had that case twice
so far and no way to trigger it.

>=20
> Have you tried raw image files?  In other words, do you know that the
> corruption only happens with qcow2?

Will do right now.

thanks a lot!

--=20
stepping stone GmbH
Neufeldstrasse 9
CH-3012 Bern
Telefon: +41 31 332 53 63
www.stepping-stone.ch
tiziano.mueller@stepping-stone.ch