From: Christoph Hellwig <hch@lst.de>
To: Peter Lieven <pl@dlh.net>
Cc: Christoph Hellwig <hch@lst.de>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: virtio-blk XFS corruption
Date: Sat, 25 Sep 2010 17:58:12 +0200 [thread overview]
Message-ID: <20100925155812.GA22144@lst.de> (raw)
In-Reply-To: <9A9D7C10-FA72-4AB5-AF4A-077109B343E5@dlh.net>
On Sat, Sep 25, 2010 at 05:40:34PM +0200, Peter Lieven wrote:
>
> Am 25.09.2010 um 17:37 schrieb Christoph Hellwig:
>
> > FYI, qemu 0.12.2 is missing:
>
> you mean 0.12.4 not 0.12.2, don't you?
Yes, sorry. (but 0.12.2 is of course missing it, too..)
> > which in the past was very good at triggering XFS guest corruption.
> > Please try with the patch applied or even better latests qemu from git.
> >
>
> i'm just trying with 0.12.5.
>
> i'm not so familiar with git. is there a command to pull only patches
> that are marked as stable and will be in the next official release?
All the qemu stable releases are tagged and you can check do
git-checkout v0.12.5
but that's not the main git HEAD which would also be interesting.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Peter Lieven <pl@dlh.net>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Christoph Hellwig <hch@lst.de>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: virtio-blk XFS corruption
Date: Sat, 25 Sep 2010 17:58:12 +0200 [thread overview]
Message-ID: <20100925155812.GA22144@lst.de> (raw)
In-Reply-To: <9A9D7C10-FA72-4AB5-AF4A-077109B343E5@dlh.net>
On Sat, Sep 25, 2010 at 05:40:34PM +0200, Peter Lieven wrote:
>
> Am 25.09.2010 um 17:37 schrieb Christoph Hellwig:
>
> > FYI, qemu 0.12.2 is missing:
>
> you mean 0.12.4 not 0.12.2, don't you?
Yes, sorry. (but 0.12.2 is of course missing it, too..)
> > which in the past was very good at triggering XFS guest corruption.
> > Please try with the patch applied or even better latests qemu from git.
> >
>
> i'm just trying with 0.12.5.
>
> i'm not so familiar with git. is there a command to pull only patches
> that are marked as stable and will be in the next official release?
All the qemu stable releases are tagged and you can check do
git-checkout v0.12.5
but that's not the main git HEAD which would also be interesting.
next prev parent reply other threads:[~2010-09-25 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 13:43 virtio-blk XFS corruption Peter Lieven
2010-09-25 13:43 ` [Qemu-devel] " Peter Lieven
2010-09-25 14:44 ` Stefan Hajnoczi
2010-09-25 14:44 ` [Qemu-devel] " Stefan Hajnoczi
2010-09-25 15:10 ` Peter Lieven
2010-09-25 15:10 ` [Qemu-devel] " Peter Lieven
2010-09-25 15:37 ` Christoph Hellwig
2010-09-25 15:37 ` [Qemu-devel] " Christoph Hellwig
2010-09-25 15:40 ` Peter Lieven
2010-09-25 15:40 ` [Qemu-devel] " Peter Lieven
2010-09-25 15:58 ` Christoph Hellwig [this message]
2010-09-25 15:58 ` Christoph Hellwig
2010-09-25 17:18 ` Peter Lieven
2010-09-25 17:18 ` [Qemu-devel] " Peter Lieven
2010-09-25 18:11 ` Peter Lieven
2010-09-25 18:11 ` [Qemu-devel] " Peter Lieven
2010-09-26 16:00 ` Peter Lieven
2010-09-26 16:00 ` [Qemu-devel] " Peter Lieven
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=20100925155812.GA22144@lst.de \
--to=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--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.