From: Anthony Liguori <anthony@codemonkey.ws>
To: Bike & Snow <bikeandsnow@googlemail.com>
Cc: kvm@vger.kernel.org
Subject: Re: OCFS2 file system corruption with QEMU/KVM
Date: Sun, 07 Jun 2009 18:17:15 -0500 [thread overview]
Message-ID: <4A2C4A7B.3090906@codemonkey.ws> (raw)
In-Reply-To: <a0c3604a0906071036w7a49084cg9204f8f4d0310c0@mail.gmail.com>
Bike & Snow wrote:
> Hello
>
> 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.
>
What version of KVM? What command line are you using?
Regards,
Anthony Liguori
> 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.
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-06-07 23:17 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 [this message]
2009-06-08 0:55 ` Charles Duffy
2009-06-08 6:02 ` Avi Kivity
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=4A2C4A7B.3090906@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=bikeandsnow@googlemail.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.