mdbooth/libldm

ldmtool cannot parse complexity volume

Opened this issue · 1 comments

Hello,

I found bug in ldmtool.
ldmtool cannot parse complexity volume with next structure
image

In this case I get next log
ldmtool create all
[ 1.094006] raid6: sse2x1 gen() 10496 MB/s
[ 1.111058] raid6: sse2x1 xor() 8685 MB/s
[ 1.128036] raid6: sse2x2 gen() 14531 MB/s
[ 1.145004] raid6: sse2x2 xor() 10539 MB/s
[ 1.162037] raid6: sse2x4 gen() 16609 MB/s
[ 1.179006] raid6: sse2x4 xor() 10472 MB/s
[ 1.196064] raid6: avx2x1 gen() 22402 MB/s
[ 1.213005] raid6: avx2x1 xor() 17525 MB/s
[ 1.230032] raid6: avx2x2 gen() 28039 MB/s
[ 1.247005] raid6: avx2x2 xor() 19593 MB/s
[ 1.264035] raid6: avx2x4 gen() 30679 MB/s
[ 1.281050] raid6: avx2x4 xor() 20357 MB/s
[ 1.281558] raid6: using algorithm avx2x4 gen() 30679 MB/s
[ 1.282136] raid6: .... xor() 20357 MB/s, rmw enabled
[ 1.282697] raid6: using avx2x2 recovery algorithm
[ 1.283261] tsc: Refined TSC clocksource calibration: 3000.048 MHz
[ 1.284180] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2b3e72cea23, max_idle_ns: 440795323402 ns
[ 1.289159] xor: automatically using best checksumming function avx
[ 1.291721] async_tx: api initialized (async)
[ 1.317100] device-mapper: raid: Loading target version 1.13.2
[ 1.318409] device-mapper: raid: Ignoring chunk size parameter for RAID 1
[ 1.319542] device-mapper: raid: Choosing default region size of 4MiB
[ 1.320236] device-mapper: table: 253:3: raid: Component device(s) too small
[ 1.320892] device-mapper: ioctl: error adding target to table
Unable to create volume Volume1 in disk group 83cd2cdf-a4d0-11e8-9c37-52540060c947: ldm_vol_DESKTOP-QIB64G9-Dg1_Volume1: Stacking NODE_DEL [verify_udev]
[
]

Thank you.

Same situation when trying to read a mirrored volume which is created under windows 10 system.