Linux Device Mapper development
 help / color / mirror / Atom feed
From: Curtis Gedak <gedakc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Cc: parted-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org,
	device-mapper development
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org,
	Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>,
	Debian LVM Team
	<pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org>
Subject: Re: [dm-devel] What is the deal with the partition separator?
Date: Wed, 16 Feb 2011 10:19:59 -0700	[thread overview]
Message-ID: <4D5C073F.3020502@gmail.com> (raw)
In-Reply-To: <4D5B7ED9.20304-l3A5Bk7waGM@public.gmane.org>

On 11-02-16 12:38 AM, Hannes Reinecke wrote:
> On 02/16/2011 04:21 AM, Phillip Susi wrote:
>> It used to be that partitions device names just had a digit added on to
>> the base disk device name.  It seems that this became problematic at
>> some point with device mapper and oddly named disks, and there have been
>> several responses to it:
>>
>> 1)  dmraid and (lib)parted now always add a 'p' between the base name
>> and the partition number

Only newer versions of (lib)parted which link with the dmraid library 
work this way with dmraid devices.  In this situation it is the dmraid 
library that is coming up with the device names.  For all other devices, 
(lib)parted uses the "linux scheme since the dawn of time" mentioned 
below.  Older versions of (lib)parted follow the "linux scheme since the 
dawn of time".

>> 2)  kpartx from multipath-tools adds the 'p' only if the base name ends
>> in a digit

kpartx follows the "linux scheme since the dawn of time" mentioned below.

>> 4)  gparted now explicitly tells dmraid to not use any character so that
>> it behaves like older versions and is therefore compatible with the
>> kpartx method that gparted has adopted, at least when the base name does
>> not end with a digit.
>>

GParted uses (lib)parted to come up with device names, except in the 
case of dmraid devices.  Because dmraid does not follow the "linux 
scheme since the dawn of time", gparted calls dmraid directly to create 
names following the old dmraid standard (only append partition number to 
device name).  If kpartx is available, then GParted will call kpartx to 
ensure that dmraid device names follow the "linux scheme since the dawn 
of time".  This behaviour enables GParted to work with all versions of 
dmraid, and maintain compatibility with (lib)parted versions 1.7.1 and 
higher.

>> Each of these components needs to agree on what the correct name is or
>> chaos ensues.  I would like to discuss the merits of each and try to
>> decide on a standard.
>>
>> Having thought about it for a moment, it seems to me that deciding on
>> always adding the 'p' is the way to go, since the 'art' just makes
>> things longer for no good reason, and if you only sometimes add the 'p'
>> then you can't tell if a device name that ends in a digit that does not
>> follow a 'p' is a whole disk, or a partition.
>>
> No.
>
> The linux scheme since the dawn of time is to
> a) Add the partition number to the device node name
> b) If last letter of the device node name is a number, insert a 'p'
> between device node name and partition number
>
> with the advent of persistent device names (via udev) the partition
> separator (for persistent links only!) is '-part'.
>
> So you have
>
> /dev/sda
> /dev/sda1
> /dev/disk/by-id/scsi-0WhatAStupidName
> /dev/disk/by-id/scsi-0WhatAStupidName-part1
>
> persistent device names are longish anyway, so we can as well use
> something readable for partitions.
>
>

My thoughts are that if possible, tools should try to create partition 
names using the "linux scheme since the dawn of time", unless there are 
good reasons to not do this.

Regards,
Curtis Gedak
(Maintainer of GParted)

  parent reply	other threads:[~2011-02-16 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16  3:21 What is the deal with the partition separator? Phillip Susi
2011-02-16  7:38 ` Hannes Reinecke
     [not found]   ` <4D5B7ED9.20304-l3A5Bk7waGM@public.gmane.org>
2011-02-16 17:19     ` Curtis Gedak [this message]
     [not found]       ` <4D5C073F.3020502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-16 19:33         ` [dm-devel] " Phillip Susi
     [not found]           ` <4D5C268B.6070507-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-16 20:18             ` Curtis Gedak
2011-02-16 19:37     ` Phillip Susi
     [not found]       ` <4D5C2793.1020601-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17  7:29         ` Hannes Reinecke
     [not found]           ` <4D5CCE75.5090202-l3A5Bk7waGM@public.gmane.org>
2011-02-17 14:57             ` Phillip Susi
     [not found]               ` <4D5D375F.9070106-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17 15:13                 ` Hannes Reinecke
     [not found]                   ` <4D5D3B34.4000005-l3A5Bk7waGM@public.gmane.org>
2011-02-17 15:13                     ` Phillip Susi
2011-02-17 16:53                       ` Alasdair G Kergon
2011-02-17 16:58                         ` Alasdair G Kergon
     [not found]                         ` <20110217165332.GE28729-FDJ95KluN3Z0klwcnFlA1dvLeJWuRmrY@public.gmane.org>
2011-02-20  5:04                           ` [dm-devel] " Phillip Susi
2011-02-17 16:54                     ` Curtis Gedak

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=4D5C073F.3020502@gmail.com \
    --to=gedakc-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hare-l3A5Bk7waGM@public.gmane.org \
    --cc=parted-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
    --cc=pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
    --cc=psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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