Summary: | sys-fs/multipath-tools-0.4.8: kpartx generates bad output on extended partitions | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nathan Bain <nebain> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | gentoo, just_john |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
command results with multipath 0.4.7-r2
command results with multipath 0.4.8 |
Description
Nathan Bain
2009-05-07 19:05:11 UTC
need more info. Can you provide your /proc/partitions with multipath active, as well as the udev info dump for the multipath device? In both 0.4.7 AND 0.4.8-r1. Created attachment 209195 [details]
command results with multipath 0.4.7-r2
Created attachment 209201 [details]
command results with multipath 0.4.8
Here are the commands for the differents multipath version. But with multipath 0.4.8 and boot on SAN I can't add mapping of /usr and /var (in initramfs) so I cannot run parted and multipath (libaio is not present after boottime). The problem is completely outside of udev. kpartx seems to break parsing the extended partition table explicitly. # kpartx -l /dev/sda sda1 : 0 524288 /dev/sda 128 sda2 : 0 10485760 /dev/sda 524416 sda3 : 0 1453828654 /dev/sda 11010176 sda5 : 0 50331713 /dev/dm-2 63 sda6 : 0 1403496815 /dev/dm-2 50331839 # sfdisk -xqL -d /dev/sda Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. # partition table of /dev/sda unit: sectors /dev/sda1 : start= 128, size= 524288, Id=83, bootable /dev/sda2 : start= 524416, size= 10485760, Id=83 /dev/sda3 : start= 11010176, size=1453828654, Id= 5 /dev/sda4 : start= 0, size= 0, Id= 0 /dev/sda5 : start= 11010239, size= 50331713, Id=82 - : start= 61341952, size=1403496878, Id= 5 - : start= 11010176, size= 0, Id= 0 - : start= 11010176, size= 0, Id= 0 /dev/sda6 : start= 61342015, size=1403496815, Id=8e - : start= 61341952, size= 0, Id= 0 - : start= 61341952, size= 0, Id= 0 - : start= 61341952, size= 0, Id= 0 0.4.8-r2 has a fix for kpart's bad extended partition handling now. I've submitted it to upstream as well, as it's present in their git tip as well. As for the DM_TABLE_STATE rule, that's still what upstream has, and while it doesn't actually do anything, I think it's not relevant to the real matter in this bug. Partitions not appearing is dues to checking ENV{DM_STATE} instead of ENV{DM_STATUS} on lines 29 and 31 of 66-kpartx.rules. |