All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: lvm-devel@redhat.com
Cc: ceph-devel@vger.kernel.org
Subject: [PATCH] devices: recognise rbd devices
Date: Wed, 16 Aug 2017 18:22:05 +0200	[thread overview]
Message-ID: <1502900525-23375-1-git-send-email-idryomov@gmail.com> (raw)

Under single_major scheme introduced in kernel 3.14, rbd devices
support up to 16 partitions.  In pre-single_major mode, rbd driver
takes up the whole major.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
---
 WHATS_NEW                 | 1 +
 lib/device/device-types.h | 1 +
 2 files changed, 2 insertions(+)

diff --git a/WHATS_NEW b/WHATS_NEW
index c8f072f3c387..b1f16cb054b5 100644
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
 Version 2.02.174 - 
 =================================
+  Recognise RADOS block devices (RBD) in filter.
   Fix check for 2nd mda at end of disk fits if using pvcreate --restorefile.
   Use maximum metadataarea size that fits with pvcreate --restorefile.
   Always clear cached bootloaderarea when wiping label e.g. in pvcreate.
diff --git a/lib/device/device-types.h b/lib/device/device-types.h
index 2834cd11fd3a..57b430173e56 100644
--- a/lib/device/device-types.h
+++ b/lib/device/device-types.h
@@ -64,5 +64,6 @@ static const dev_known_type_t _dev_known_types[] = {
 	{"nvme", 64, "NVM Express"},
 	{"zvol", 16, "ZFS Zvols"},
 	{"VxDMP", 16, "Veritas Dynamic Multipathing"},
+	{"rbd", 16, "RADOS block device (RBD)"},
 	{"", 0, ""}
 };
-- 
2.4.3


WARNING: multiple messages have this Message-ID (diff)
From: Ilya Dryomov <idryomov@gmail.com>
To: lvm-devel@redhat.com
Subject: [PATCH] devices: recognise rbd devices
Date: Wed, 16 Aug 2017 18:22:05 +0200	[thread overview]
Message-ID: <1502900525-23375-1-git-send-email-idryomov@gmail.com> (raw)

Under single_major scheme introduced in kernel 3.14, rbd devices
support up to 16 partitions.  In pre-single_major mode, rbd driver
takes up the whole major.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
---
 WHATS_NEW                 | 1 +
 lib/device/device-types.h | 1 +
 2 files changed, 2 insertions(+)

diff --git a/WHATS_NEW b/WHATS_NEW
index c8f072f3c387..b1f16cb054b5 100644
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
 Version 2.02.174 - 
 =================================
+  Recognise RADOS block devices (RBD) in filter.
   Fix check for 2nd mda at end of disk fits if using pvcreate --restorefile.
   Use maximum metadataarea size that fits with pvcreate --restorefile.
   Always clear cached bootloaderarea when wiping label e.g. in pvcreate.
diff --git a/lib/device/device-types.h b/lib/device/device-types.h
index 2834cd11fd3a..57b430173e56 100644
--- a/lib/device/device-types.h
+++ b/lib/device/device-types.h
@@ -64,5 +64,6 @@ static const dev_known_type_t _dev_known_types[] = {
 	{"nvme", 64, "NVM Express"},
 	{"zvol", 16, "ZFS Zvols"},
 	{"VxDMP", 16, "Veritas Dynamic Multipathing"},
+	{"rbd", 16, "RADOS block device (RBD)"},
 	{"", 0, ""}
 };
-- 
2.4.3



             reply	other threads:[~2017-08-16 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 16:22 Ilya Dryomov [this message]
2017-08-16 16:22 ` [PATCH] devices: recognise rbd devices Ilya Dryomov
2017-08-31 14:10 ` Ilya Dryomov
2017-08-31 14:10   ` Ilya Dryomov

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=1502900525-23375-1-git-send-email-idryomov@gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=lvm-devel@redhat.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.