dmraid creates too small of a device (32-bit truncation)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dmraid (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Device mapper goes bananas on the provided table:
[ 1.530703] device-mapper: table: 252:4: dm-0 too small for target: start=268699648, len=9792587776, dev_size=2545099264
[ 1.530985] device-mapper: table: 252:4: dm-0 too small for target: start=10061287424, len=1073745408, dev_size=2545099264
As can be seen, the actual device created is too small:
# dmraid -r
/dev/sdc: isw, "isw_dbjcghcgcd", GROUP, ok, 5860533166 sectors, data@ 0
/dev/sdb: isw, "isw_dbjcghcgcd", GROUP, ok, 5860533166 sectors, data@ 0
# dmraid -s
*** Group superset isw_dbjcghcgcd
--> Active Subset
name : isw_dbjcghcgcd_
size : 2545099264
stride : 256
type : stripe
status : ok
subsets: 0
devs : 2
spares : 0
2545099264 = 0x97B32200
Using the following on dmsetup works:
0 11135033344 striped 2 256 /dev/sdb 0 /dev/sdc 0
11135033344 = 0x297B32000
The GPT partition does not have that last 512 blocks listed and parted would complain otherwise.
Related to https:/ /bugs.launchpad .net/ubuntu/ +source/ dmraid/ +bug/599255 but the end conclusion there seems to be a controller issue.