FS#56758 - libblockdev 2.14-2 breaks ldm (Dynamic disks)

Attached to Project: Arch Linux
Opened by Steven De Bondt (eggz) - Sunday, 17 December 2017, 20:00 GMT
Last edited by Antonio Rojas (arojas) - Monday, 18 December 2017, 16:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When upgrading from libblockdev 2.14-1 to libblockdev 2.14-2, my Dynamic disk, being a striped volume consisting of 2 physical disks, stops being represented in the device mapper. ldmtool still detects the volume, but I am unable to create a device mapping for it.

Downgrading to 2.14-1 fixes this problem and my dynamic volume gets autmaticly mounted again via the old fstab entry without any need of manual intervention, so clearly, the devicemapping works again provided by ldmtool.service.

Additional info:
libblockdev 2.14-2

It's a striped volume created in windows with NTFS on it, but since this problem happens at blocklevel the FS shoudnt really matter.

Steps to reproduce:

Introduce a dynamic disk with this layout to an arch linux system using libblockdev 2.14-2:

[ !1639 ] eggzpc ~ # ldmtool scan
[
"f4cf963f-161f-11e7-8eb5-ac9e174c2ec9"
]
[ !1636 ] eggzpc ~ # ldmtool show diskgroup f4cf963f-161f-11e7-8eb5-ac9e174c2ec9
{
"name" : "DESKTOP-AQ45VSG-Dg0",
"guid" : "f4cf963f-161f-11e7-8eb5-ac9e174c2ec9",
"volumes" : [
"Volume1"
],
"disks" : [
"Disk1",
"Disk2"
]
}

then do this:
ldmtool create all

Nothing will happen, and /dev/mapper will remain empty.
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 18 December 2017, 16:44 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Monday, 18 December 2017, 11:04 GMT
which version of cryptsetup do you have installed?
Comment by Steven De Bondt (eggz) - Monday, 18 December 2017, 16:32 GMT
I Upgraded to libblockdev 2.14-2 again to reproduce the situation but it works this time. I though cryptsetup was always at version 2.0.0-1 from the very beginning of the situation but clearly I'm wrong or missing something:

( [2017-12-14 20:59] [ALPM] upgraded cryptsetup (1.7.5-2 -> 2.0.0-1) )

Clearly something went wrong that I did not and still not see.

Thank you for your attention and sorry for taking your time.

Loading...