From: Avi Kivity <avi@redhat.com>
To: Charles Duffy <Charles_Duffy@messageone.com>
Cc: kvm@vger.kernel.org
Subject: Re: OCFS2 file system corruption with QEMU/KVM
Date: Mon, 08 Jun 2009 09:02:28 +0300 [thread overview]
Message-ID: <4A2CA974.6020604@redhat.com> (raw)
In-Reply-To: <h0hni7$r1u$1@ger.gmane.org>
Charles Duffy wrote:
> Bike & Snow wrote:
>> Is anyone using OCFS2 on a SAN based setup (in my case iSCSI) for a
>> shared storage setup for KVM?
>>
>> I've got a really nice setup that works really well and gives very
>> good performance.
>>
>> However, the QEMU disk images (raw format) keep corrupting.
>>
>> Is OCFS2 to be avoided in the setup or are there any workarounds? For
>> example filesystem setup.
>
> I've had no trouble using GFS2. Are you setting cache=off?
Shouldn't the caches on GFS/OCFS be coherent?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-06-08 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 17:36 OCFS2 file system corruption with QEMU/KVM Bike & Snow
2009-06-07 23:17 ` Anthony Liguori
2009-06-08 0:55 ` Charles Duffy
2009-06-08 6:02 ` Avi Kivity [this message]
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=4A2CA974.6020604@redhat.com \
--to=avi@redhat.com \
--cc=Charles_Duffy@messageone.com \
--cc=kvm@vger.kernel.org \
/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.