ISST-LTE: parted command shows "device-mapper: table ioctl on failed: No such device or address" error

[bugproxy]

[Impact]
Partitioning multipath devices after install always results in multiple error messages even though the devices get created.

[Test case]
Run the following command:
parted -s /dev/mapper/mpath1 mkpart primary 0% 20%
On a system where mpath1 is an extra unpartitioned multipath device.

[Regression Potential]
This should generally not adversely affect partitioning devices; the goal is to make sure parted correctly synchronizes with udev and multipath-tools so that device nodes are created at the right moment to satisfy what parted attempts to do, and that they are only created by udev, not automatically via device-mapper.

Since this only affects timing of device node creation and only in the device-mapper case, where it already appears to be incorrect, there should be no other effect than removing the error messages.

----

== Comment: #0 - Manjunatha H R <email address hidden> - 2016-01-19 03:02:12 ==
On Ubuntu14.04.4 while creating disk partition using parted command following error/message is displayed:

root@roselp1:~# parted -s /dev/mapper/mpath2 mkpart primary 0% 20%
Device /dev/mapper/mpath2p1 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath2p1 not found
device-mapper: table ioctl on failed: No such device or address

Even though mpath2p1 is created , Device /dev/mapper/mpath2p1 not found error is shown:

root@roselp1:~# lsblk /dev/mapper/mpath2
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mpath2 (dm-2) 252:2 0 20G 0 mpath
??mpath2p1 (dm-12) 252:12 0 4G 0 dm

root@roselp1:~# ls /dev/mapper/mpath2*
/dev/mapper/mpath2 /dev/mapper/mpath2p1

uname -a:
--------------
root@roselp1:~# uname -a
Linux roselp1 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

multipath packages installed:
--------------------------------------
root@roselp1:~# dpkg -l|grep multipath
ii multipath-tools 0.4.9-3ubuntu7.7 ppc64el maintain multipath block device access
ii multipath-tools-boot 0.4.9-3ubuntu7.7 all Support booting from multipath devices

parted packages installed:
-----------------------------------
root@roselp1:~# dpkg -l|grep parted
ii libparted0debian1:ppc64el 2.3-19ubuntu1.14.04.1 ppc64el disk partition manipulator - shared library
ii parted 2.3-19ubuntu1.14.04.1 ppc64el disk partition manipulator

Steps to recreate:
-------------------------
1. Install Ubuntu14.04.4 on a PowerVM lpar with multipath disks.
2. Create partition using parted command: parted -s <mpath device> mkpart primary 0% 20% ----> This shows "device-mapper: table ioctl on failed" , even though partition is created.

Contact info:
------------------
Manju (<email address hidden>) A.P (<email address hidden>)

== Comment: #2 - Manjunatha H R <email address hidden> - 2016-01-19 03:06:48 ==

== Comment: #4 - Manjunatha H R <email address hidden> - 2016-01-19 06:13:20 ==
For getting "udevadm monitor -p" output , I had to create one more partition and whose output is :

root@roselp1:~# lsblk /dev/mapper/mpath2
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mpath2 (dm-2) 252:2 0 20G 0 mpath
??mpath2p1 (dm-12) 252:12 0 4G 0 dm
root@roselp1:~# parted -s /dev/mapper/mpath2 mkpart primary 20% 40%
Device /dev/mapper/mpath2p2 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath2p2 not found
device-mapper: table ioctl on failed: No such device or address
root@roselp1:~#

root@roselp1:~# udevadm monitor -p
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[18452.366922] add /devices/virtual/bdi/252:13 (bdi)
ACTION=add
DEVPATH=/devices/virtual/bdi/252:13
SEQNUM=3096
SUBSYSTEM=bdi

KERNEL[18452.367085] add /devices/virtual/block/dm-13 (block)
ACTION=add
DEVNAME=/dev/dm-13
DEVPATH=/devices/virtual/block/dm-13
DEVTYPE=disk
MAJOR=252
MINOR=13
SEQNUM=3097
SUBSYSTEM=block

KERNEL[18452.369054] change /devices/virtual/block/dm-13 (block)
ACTION=change
DEVNAME=/dev/dm-13
DEVPATH=/devices/virtual/block/dm-13
DEVTYPE=disk
DM_COOKIE=4390912
MAJOR=252
MINOR=13
SEQNUM=3098
SUBSYSTEM=block

UDEV [18452.369499] add /devices/virtual/bdi/252:13 (bdi)
ACTION=add
DEVPATH=/devices/virtual/bdi/252:13
SEQNUM=3096
SUBSYSTEM=bdi
USEC_INITIALIZED=452366903

UDEV [18452.377916] add /devices/virtual/block/dm-13 (block)
ACTION=add
DEVNAME=/dev/dm-13
DEVPATH=/devices/virtual/block/dm-13
DEVTYPE=disk
DM_NAME=mpath2p2
DM_UDEV_DISABLE_DISK_RULES_FLAG=1
DM_UDEV_DISABLE_OTHER_RULES_FLAG=1
DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
MAJOR=252
MINOR=13
SEQNUM=3097
SUBSYSTEM=block
USEC_INITIALIZED=452367384

UDEV [18452.510578] change /devices/virtual/block/dm-13 (block)
ACTION=change
DEVLINKS=/dev/disk/by-id/dm-name-mpath2p2
DEVNAME=/dev/dm-13
DEVPATH=/devices/virtual/block/dm-13
DEVTYPE=disk
DM_COOKIE=4390912
DM_NAME=mpath2p2
DM_SUSPENDED=0
DM_UDEV_DISABLE_DM_RULES_FLAG=1
DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
DM_UDEV_PRIMARY_SOURCE_FLAG=1
DM_UDEV_RULES=1
MAJOR=252
MINOR=13
SEQNUM=3098
SUBSYSTEM=block
USEC_INITIALIZED=452367384

----------------------------------------------------

> Hi Manju,
>
>
> The disk management tool parted is GNU provided tool. Ubuntu has these tools
> packaged in util-linux, which is maintained by ubuntu. Can you please try
> util-linux tools (eg, fdisk, partx) and test if the same issue can be
> replicated?

Thanks Chandan..

Tried fdisk and partx which are part of "util-linux"

1. fdisk creates partition without any error message:
------------------------------
root@roselp1:~# fdisk /dev/mapper/mpath1

Command (m for help): n
Partition type:
   p primary (0 primary, 0 extended, 4 free)
   e extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-41943039, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 4096

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

2. partx FAILS to add the dev mapping of the newly created partition:
----------------------------------------------
root@roselp1:~# partx -a /dev/mapper/mpath1
partx: /dev/mapper/mpath1: error adding partition 1

root@roselp1:~# lsblk /dev/mapper/mpath1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mpath1 (dm-1) 252:1 0 20G 0 mpath

To Create device maps after partition creation, we will have to relay on GNU packages: partprobe or kpartx

Output of partprobe :
-------------------------
root@roselp1:~# partprobe /dev/mapper/mpath1
Device /dev/mapper/mpath1p1 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath1p1 not found
device-mapper: table ioctl on failed: No such device or address
root@roselp1:~#

Output of kpartx:
---------------------
root@roselp1:~# kpartx -a /dev/mapper/mpath1
root@roselp1:~# lsblk /dev/mapper/mpath1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mpath1 (dm-1) 252:1 0 20G 0 mpath
??mpath1p1 (dm-21) 252:21 0 1M 0 part

Just with "util-linux" tools (eg, fdisk, partx), partition creation and device maps fails. Only way to get the dev map for the partition created is to relay on GNU tools: partprobe OR kpartx.

Does util-linux's partx required to be fixed ?

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1536008/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Langasek (vorlon)]

Mathieu, does this symptom look familiar to you?

[Mathieu Trudel-Lapierre (cyphermox)]

Yes. It looks a lot like another bug we have for parted due to parted and kpartx fighting over who should create the device nodes. I'll review this and mark as duplicate as applicable.

[Phillip Susi (psusi)]

I was going to go mark it as a duplicate but now I can't find that other bug.

[Mathieu Trudel-Lapierre (cyphermox)]

Well, it's the same kind of idea, but I would rather not make them duplicates anyway. The other bug would be bug 1473903.

[Mathieu Trudel-Lapierre (cyphermox)]

I managed to find a patch I'm testing now, which adds udev sync support to parted 2.3 (in 14.04) which is already in parted 3.2.

Testing is in progress, this should help remove the "device is busy" warnings.

[Mathieu Trudel-Lapierre (cyphermox)]

As far as I can tell this doesn't show up on xenial.

[Adam Conrad (adconrad)]

Hello bugproxy, or anyone else affected,

Accepted parted into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/parted/2.3-19ubuntu1.14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-02-04 08:39 EDT-------
(In reply to comment #16)
> Hello bugproxy, or anyone else affected,
>
> Accepted parted into trusty-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/parted/2.3-19ubuntu1.14.04.2 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Your feedback will aid us getting this update out
> to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, and change the tag from
> verification-needed to verification-done. If it does not fix the bug for
> you, please add a comment stating that, and change the tag to
> verification-failed. In either case, details of your testing will help us
> make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance!

On Power Machine with Ubuntu14.04.4, the above patch did not help to resolve the parted command issue:

Installed package:
-------------------------
root@miglp2:~# dpkg -l|grep parted
ii libparted0debian1:ppc64el 2.3-19ubuntu1.14.04.2 ppc64el disk partition manipulator - shared library
ii parted 2.3-19ubuntu1.14.04.2 ppc64el disk partition manipulator

parted command shows ioctl fail message:
-------------------------
root@miglp2:~# parted -s /dev/mapper/mpath2 mkpart primary 20% 40%
Device /dev/mapper/mpath2-part2 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath2-part2 not found
device-mapper: table ioctl on failed: No such device or address

As reported earlier, partx also fails:
-----------------------------
root@miglp2:~# partx -a /dev/mapper/mpath2
partx: /dev/mapper/mpath2: error adding partitions 1-2
root@miglp2:~# echo $?
1

Thanks,
Manju

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2016-02-04 08:41 EDT-------

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-02-11 11:05 EDT-------
Moving to verification-failed according to the last update.

[Phillip Susi (psusi)]

Wait, now it is looking for /dev/mapper/mpath2-part1 instead of mpath2p1?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-02-21 10:14 EDT-------
> Wait, now it is looking for /dev/mapper/mpath2-part1 instead of mpath2p1?

Yes, parted command looks for "-part1" instead "p1".

Following are the observations:
--------------
1. When only parted package is updated to "2.3-19ubuntu1.14.04.2" version:
root@highlp6:~# dpkg -l |grep parted
ii libparted0debian1:ppc64el 2.3-19ubuntu1.14.04.1
ii parted 2.3-19ubuntu1.14.04.2

parted command shows:
root@highlp6:~# parted -s /dev/mapper/mpath0 mkpart primary 0% 20%
Device /dev/mapper/mpath0p1 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath0p1 not found
device-mapper: table ioctl on failed: No such device or address
root@highlp6:~#

2. When both "parted" and "libparted0debian1" are updated to "2.3-19ubuntu1.14.04.2"
root@highlp6:~# dpkg -l |grep parted
ii libparted0debian1:ppc64el 2.3-19ubuntu1.14.04.2
ii parted 2.3-19ubuntu1.14.04.2

parted command shows:
root@highlp6:~# parted -s /dev/mapper/mpath0 mkpart primary 0% 20%
Device /dev/mapper/mpath0-part1 not found
device-mapper: table ioctl on failed: No such device or address
Device /dev/mapper/mpath0-part1 not found
device-mapper: table ioctl on failed: No such device or address

Thanks,
Manju

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-03-10 10:03 EDT-------
Hi,

Any updates on this bug ?? Issue is seen on Ubuntu16.04 too..

Thanks,
Manju

[Mathieu Trudel-Lapierre (cyphermox)]

We'll need to re-test this. I was not getting the issue on 16.04 at all, and although I can reproduce it on 14.04, it doesn't appear to be breaking anything (things still are getting done by parted). Could be a race where things are being attempted, fail, show the message, and are then retried?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-04-05 07:13 EDT-------
Issue is no longer seen on Ubuntu16.04

root@roselp1:~# parted -s /dev/mapper/mpathb mkpart primary 0% 20%
root@roselp1:~#
root@roselp1:~# parted -s /dev/mapper/mpathc mkpart primary 0% 20%
root@roselp1:~#

root@roselp1:~# uname -r
4.4.0-16-generic

root@roselp1:~# dpkg -l |grep multipath
ii multipath-tools 0.5.0+git1.656f8865-5ubuntu1 ppc64el maintain multipath block device access
ii multipath-tools-boot 0.5.0+git1.656f8865-5ubuntu1 all Support booting from multipath devices

root@roselp1:~# dpkg -l|grep parted
ii libparted2:ppc64el 3.2-15 ppc64el disk partition manipulator - shared library
ii parted 3.2-15 ppc64el disk partition manipulator

Thanks,
Manju

[Martin Pitt (pitti)]

The version of parted in the proposed pocket of Trusty that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.