From: Danny Kukawka <danny.kukawka@bisect.de>
To: ceph-devel@vger.kernel.org
Cc: Tommi Virtanen <tv@inktank.com>
Subject: Re: [PATCH] make mkcephfs and init-ceph osd filesystem handling more flexible
Date: Thu, 09 Aug 2012 18:49:01 +0200 [thread overview]
Message-ID: <5023E9FD.2060501@bisect.de> (raw)
In-Reply-To: <CADvuQRGLUpPT=RxYqptGq+9Ku2dNiKLsdY8a=KjjfoquucBc7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Am 09.08.2012 18:26, schrieb Tommi Virtanen:
> On Thu, Aug 9, 2012 at 8:42 AM, Danny Kukawka <danny.kukawka@bisect.de> wrote:
>> Remove btrfs specific keys and replace them by more generic
>> keys to be able to replace btrfs with e.g. xfs or ext4 easily.
>>
>> Add new key to define the osd fs type: 'fstype', which can get
>> defined in the [osd] section for all OSDs.
>
> I'm going to say let's not do this. In fact, I've wanted to remove the
> "btrfs devs" option for a while now, as it keeps leading people down
> the wrong path:
> https://github.com/ceph/ceph/commits/kill-btrfs-devs
>
> mkcephfs is not a viable route forward. For example, it is unable to
> expand a pre-existing cluster.
>
> The new "OSD hotplugging" style init is much, much nicer. And does
> more than just mkfs & mount.
And where can I find this new "OSD hotplugging" style init? Is there any
documentation?
Danny
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-08-09 16:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 15:42 [PATCH] make mkcephfs and init-ceph osd filesystem handling more flexible Danny Kukawka
2012-08-09 16:26 ` Tommi Virtanen
2012-08-09 16:46 ` Jim Schutt
2012-08-09 16:53 ` Tommi Virtanen
2012-08-09 17:03 ` Danny Kukawka
2012-08-09 17:12 ` Tommi Virtanen
2012-08-10 1:53 ` Sage Weil
2012-08-10 2:01 ` Xiaopong Tran
2012-08-09 16:49 ` Danny Kukawka [this message]
2012-08-09 16:54 ` Tommi Virtanen
2012-08-10 15:54 ` Sage Weil
2012-08-10 16:03 ` Danny Kukawka
2012-08-10 16:12 ` Sage Weil
2012-08-10 16:57 ` Mandell Degerness
2012-08-16 22:32 ` Sage Weil
2012-08-16 22:52 ` Tommi Virtanen
2012-08-16 22:55 ` Tommi Virtanen
2012-08-16 23:40 ` Sage Weil
2012-11-02 9:58 ` Danny Al-Gaaf
2012-11-02 11:13 ` Sage Weil
2012-11-15 0:12 ` Sage Weil
2012-11-15 10:32 ` Danny Al-Gaaf
2012-11-15 15:05 ` Sage Weil
2012-11-21 0:23 ` Sage Weil
2012-11-21 10:20 ` Danny Al-Gaaf
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=5023E9FD.2060501@bisect.de \
--to=danny.kukawka@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=tv@inktank.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.