public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] OT: btrfs and qemu
Date: Thu, 08 Nov 2012 08:12:02 +0800	[thread overview]
Message-ID: <1352333522.14577.7.camel@moriah> (raw)

I am testing a small ceph cluster implemented in qemu-kvm and seeing
there are a few cloudy types here who may have tried this, I though I'd
ask about my problem before reworking.

I decided to go btrfs in the VM's and the ceph storage (all qcow2) on a
reiserfs host fs.

So far so good, but I am getting btrfs problems - throws an error and
goes readonly -> oops/crash in btrfs


I am now using cache=none for qemu (which is recommended for vm's on a
btrfs host, though not the case here) and that helped some.

My question is ... are there any other settings to help this
configurations stability/reliability using in vm btrfs?

Otherwise I'll go back to reiserfs for the hosts and try xfs for the
ceph storage.

BillK



                 reply	other threads:[~2012-11-08  0:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1352333522.14577.7.camel@moriah \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox