From: Wido den Hollander <wido@42on.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Partitions on bcache devices
Date: Thu, 29 Sep 2016 17:38:38 +0200 (CEST) [thread overview]
Message-ID: <225072061.5367.1475163518820@ox.pcextreme.nl> (raw)
In-Reply-To: <20160929160903.10b63b45@harpe.intellique.com>
> Op 29 september 2016 om 16:09 schreef Emmanuel Florac <eflorac@intellique.com>:
>
>
> 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 :)
>
Thanks for the information :) Currently not really a option with Ceph.
> 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.
>
Yes, I'm sure. You can create the partitions, but they will not show up as devices which you can use due to a limitation in the bcache kernel driver.
Patches [0] are out there to make this work, but they are not in bcache yet.
Hence my thread if this support can be added.
Wido
[0]: https://yaple.net/2016/03/31/bcache-partitions-and-dkms/
> --
> ------------------------------------------------------------------------
> Emmanuel Florac | Direction technique
> | Intellique
> | <eflorac@intellique.com>
> | +33 1 78 94 84 02
> ------------------------------------------------------------------------
next prev parent reply other threads:[~2016-09-29 15:38 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
2016-09-29 15:38 ` Wido den Hollander [this message]
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=225072061.5367.1475163518820@ox.pcextreme.nl \
--to=wido@42on.com \
--cc=eflorac@intellique.com \
--cc=linux-bcache@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