[Bug 1427859] Re: ISST-SAN:Need a common format for partition listing using kpartx, fdisk.distrib and ls -l

Dave Heller hellerda at linux.vnet.ibm.com
Tue Mar 3 21:44:55 UTC 2015


We are seeing this naming inconsistency (mpathXpX vs. mpathX-partX) in a
few places, such as launchpad bug 1427333, which is open as a udev bug.
But the problem here is the incorrect reporting by kpartx and fdisk.
These tools should accurately reflect the device nodes as they exist,
regardless of how they were created.

In the case of kpartx maybe this is just a "label" and not intended to
reflect the exact node in /dev filesystem.   disk on the other hand is
reporting the full path (that does not exist) and that's clearly wrong.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1427859

Title:
  ISST-SAN:Need a common format for partition listing using
  kpartx,fdisk.distrib and ls -l

Status in multipath-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - LEKSHMI C. PILLAI <lekshmi.cpillai at in.ibm.com> - 2015-02-25 09:02:18 ==
  This is a KVM guest with Ubuntu 15.04.

  I am facing issues with format with partition listing using different
  commands

  In zap06 I created partitions on mpath29 using fdisk.distrib

  Before partition creation:

  root at zap06:/dev/mapper# fdisk.distrib  -l /dev/mapper/mpath29---------->
  Disk /dev/mapper/mpath29: 15 GiB, 16106127360 bytes, 31457280 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  root at zap06:/dev/mapper# kpartx -r /dev/mapper/mpath29--------------->
  root at zap06:/dev/mapper# ls -l mpath29--------------------------------->
  lrwxrwxrwx 1 root root 7 Feb 24 08:46 mpath29 -> ../dm-6
  root at zap06:/dev/mapper# 

  After Partition  creation:

  root at zap06:/dev/mapper# fdisk.distrib -l
  /dev/mapper/mpath29--------------->

  Disk /dev/mapper/mpath29: 15 GiB, 16106127360 bytes, 31457280 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0xce509b1c

  Device                Boot    Start      End  Sectors Size Id Type
  /dev/mapper/mpath29p1          2048     2048        0   0B 83 Linux
  /dev/mapper/mpath29p2          4096 10489855 10485760   5G 83 Linux
  /dev/mapper/mpath29p3      10489856 20975615 10485760   5G 83 Linux

  root at zap06:/dev/mapper# kpartx -r /dev/mapper/mpath29
  mpath29p2 : 0 10485760 /dev/mapper/mpath29 4096--------------
  mpath29p3 : 0 10485760 /dev/mapper/mpath29 10489856-------------------

  But instead of names like mpath29pX, the actual device nodes have
  names like mpath29-partX:

  root at zap06:/dev/mapper# ls -l /dev/mapper/mpath29*
  lrwxrwxrwx 1 root root       7 Feb 25 01:30 /dev/mapper/mpath29 -> ../dm-6
  brw-rw---- 1 root disk 252, 68 Feb 25 01:30 /dev/mapper/mpath29-part2
  brw-rw---- 1 root disk 252, 69 Feb 25 01:30 /dev/mapper/mpath29-part3
  root at zap06:/dev/mapper# 

  After that I created the filesystem on these partitions using the
  convention "mpath-part2".Its created successfully and I am able to
  mount it

  root at zap06:/dev/mapper# mount | grep "29"
  /dev/mapper/mpath29-part2 on /Fs29 type ext4 (rw)
  /dev/mapper/mpath29-part3 on /FS29_1 type xfs (rw)
  root at zap06:/dev/mapper# 

  Thanks
  Lekshmi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1427859/+subscriptions



More information about the foundations-bugs mailing list