public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Wido den Hollander <wido@42on.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Partitions on bcache devices
Date: Thu, 29 Sep 2016 16:09:03 +0200	[thread overview]
Message-ID: <20160929160903.10b63b45@harpe.intellique.com> (raw)
In-Reply-To: <1406388200.5277.1475090090844@ox.pcextreme.nl>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Le Wed, 28 Sep 2016 21:14:50 +0200 (CEST)
Wido den Hollander <wido@42on.com> écrivait:

> In both cases Ceph wants to create partitions on all disks it uses.
> By adding bcache in between the performance can be boosted really
> well. Fast NVM-e SSDs with some large SATA drives vastly improve
> performance.
> 
> Yes, you could use LVM in between, but that just adds more layers and
> is rather complex to accomplish with the current tooling. If bcache
> would support partitions it would all be a lot easier.
> 
> And next to Ceph there might be other tools which can benefit from
> partitions on bcache, who knows?

Two points: first I'm pretty sure LVM is the preferred method nowadays
to create volumes on disks that are not boot drives. In fact, all
enterprises distros propose to set up even the boot drive with LVM
instead of partitionning and have been doing so for 10 years. 
So I'm pretty sure having in ceph the option to use LVM instead of
partitionning would be a darn good thing :)

Second: are you absolutely sure you can't partition a bcache device?
Does parted refuse to open and partition it? In which case, you may
only be missing some appropriate udev rules.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-09-29 14:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 13:45 Partitions on bcache devices Wido den Hollander
2016-09-28 17:11 ` Emmanuel Florac
2016-09-28 19:14   ` Wido den Hollander
2016-09-29 14:09     ` Emmanuel Florac [this message]
2016-09-29 15:38       ` Wido den Hollander
2016-09-29 16:25         ` Emmanuel Florac
2016-09-29 15:40       ` Jens-U. Mozdzen
2016-09-29 16:31         ` Emmanuel Florac
2016-09-29 16:52           ` Wido den Hollander
2016-09-29 17:11             ` Emmanuel Florac
2016-10-14 12:15               ` Wido den Hollander
2016-10-14 16:02                 ` Emmanuel Florac
2016-10-24  1:19                 ` [PATCH v1] bcache: partition support: add 16 minors per major Eric Wheeler
2016-10-24  1:22                   ` [PATCH v1] bcache: partition support: add 16 minors per bcacheN device Eric Wheeler
2016-10-25  7:05                   ` [PATCH v1] bcache: partition support: add 16 minors per major Wido den Hollander
2016-09-30  8:30           ` Partitions on bcache devices Jens-U. Mozdzen

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=20160929160903.10b63b45@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=wido@42on.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox