From: "Tiziano Müller" <tiziano.mueller@stepping-stone.ch>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Silent filesystem/qcow2 corruptions with qemu-kvm-1.0 and 1.1.1
Date: Fri, 12 Oct 2012 10:53:31 +0200 [thread overview]
Message-ID: <1350032011.4696.85.camel@storm> (raw)
In-Reply-To: <20121012082831.GA14822@stefanha-thinkpad.redhat.com>
Am Freitag, den 12.10.2012, 10:28 +0200 schrieb Stefan Hajnoczi:
> On Thu, Oct 11, 2012 at 03:33:23PM +0200, Tiziano Müller wrote:
> > One test case was:
> > * xfs_repair /dev/vda2 -> corruptions found and fixed
> > * xfs_repair /dev/vda2 -> no corruptions found
>
> From here...
>
> > * mount /dev/vda2 /mnt/something
> > * find /mnt/something > /dev/null
> > * umount /mnt/something
>
> ...to here is mostly read-only.
>
> > * xfs_repair /dev/vda2 -> corruptions found again
>
> And yet corruptions are reported inside the guest!
>
> 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.
>
> 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!
--
stepping stone GmbH
Neufeldstrasse 9
CH-3012 Bern
Telefon: +41 31 332 53 63
www.stepping-stone.ch
tiziano.mueller@stepping-stone.ch
next prev parent reply other threads:[~2012-10-12 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:33 [Qemu-devel] Silent filesystem/qcow2 corruptions with qemu-kvm-1.0 and 1.1.1 Tiziano Müller
2012-10-12 8:28 ` Stefan Hajnoczi
2012-10-12 8:53 ` Tiziano Müller [this message]
2012-10-12 8:33 ` Stefan Hajnoczi
2012-10-12 8:53 ` Tiziano Müller
2012-10-15 7:48 ` Stefan Hajnoczi
2012-10-15 9:34 ` Tiziano Müller
2012-10-15 11:11 ` Kevin Wolf
2012-10-15 11:39 ` Tiziano Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350032011.4696.85.camel@storm \
--to=tiziano.mueller@stepping-stone.ch \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.