From: Peter Niemayer <niemayer@isg.de>
To: ceph-devel@vger.kernel.org
Subject: Re: Using other filesystems than btrfs with Ceph
Date: Fri, 11 Jun 2010 18:47:08 +0200 [thread overview]
Message-ID: <hutpad$p9t$1@dough.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1006110938120.20973@cobra.newdream.net>
On 06/11/2010 06:40 PM, Sage Weil wrote:
> The btrfs isn't required for consistency if the writeahead journal is
> enabled (which it is by default). However, at the moment the code that
> controls trimming the journal assumes ext3 data=ordered fsync semantics
> (fsync flushes the entire journal and all prior writes). This needs a
> little bit of work to do the right thing with ext4 and xfs.
>
> So: I would stick with btrfs or ext3 for now if you want recovery to work
> reliably!
The recovery you are referring to, here, is that an operation required...
a) after an outage that involved many/all redundant OSDs
b) after a physical failure of one underlying storage device
c) after every disconnect/reconnect of Ceph nodes
?
Regards,
Peter Niemayer
next prev parent reply other threads:[~2010-06-11 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 14:23 Using other filesystems than btrfs with Ceph Peter Niemayer
2010-06-11 16:26 ` Gregory Farnum
2010-06-11 16:40 ` Sage Weil
2010-06-11 16:47 ` Peter Niemayer [this message]
2010-06-11 16:54 ` Sage Weil
2010-06-11 16:42 ` Peter Niemayer
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='hutpad$p9t$1@dough.gmane.org' \
--to=niemayer@isg.de \
--cc=ceph-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox