From: Wido den Hollander <wido@widodh.nl>
To: martin@tuxadero.com
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Unmountable btrfs filesystems
Date: Mon, 18 Jun 2012 11:30:42 +0200 [thread overview]
Message-ID: <4FDEF542.3040704@widodh.nl> (raw)
In-Reply-To: <4FDDE1DE.5030709@tuxadero.com>
Hi,
On 06/17/2012 03:55 PM, Martin Mailand wrote:
> 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.
>
I'll give that one a try, thanks!
I've also let the btrfs tools like fsck loose on those filesystems, but
they were beyond any repair. Al kinds of errors on the filesystems.
Nothing wrong with the disk below them, but the filesystems were just
completely broken, no way of repairing.
Wido
> 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-18 9:30 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
2012-06-18 9:30 ` Wido den Hollander [this message]
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=4FDEF542.3040704@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=martin@tuxadero.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.