From: Martin Mailand <martin@tuxadero.com>
To: Wido den Hollander <wido@widodh.nl>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Unmountable btrfs filesystems
Date: Sun, 17 Jun 2012 15:55:42 +0200 [thread overview]
Message-ID: <4FDDE1DE.5030709@tuxadero.com> (raw)
In-Reply-To: <4FDCD484.50706@widodh.nl>
Hi Wido,
until recently there were still a few bugs in btrfs which could be hit
quite easily with ceph. The last big one was fixed here
http://www.spinics.net/lists/ceph-devel/msg06270.html
I am running a ceph cluster with btrfs on a 3.5-rc2 without a problem,
even under heavy test load.
Hope that's helped.
-martin
Am 16.06.2012 20:46, schrieb Wido den Hollander:
> I tried various kernels, the most recent 3.3.0 from kernel.ubuntu.com,
> but I'm still seeing this.
>
> Is anyone seeing the same or did everybody migrate away to ext4 or XFS?
>
> I still prefer btrfs due to the snapshotting, but loosing all these
> OSD's all the time is getting kind of frustrating.
>
> Any thoughts or comments?
next prev parent reply other threads:[~2012-06-17 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 18:46 Unmountable btrfs filesystems Wido den Hollander
2012-06-16 19:12 ` Mark Nelson
2012-06-22 14:47 ` Guido Winkelmann
2012-06-17 13:55 ` Martin Mailand [this message]
2012-06-18 9:30 ` Wido den Hollander
2012-06-22 14:54 ` Guido Winkelmann
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=4FDDE1DE.5030709@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@widodh.nl \
/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