Bug#586104: fails to map extended partitions

Guido Günther agx at sigxcpu.org
Wed Jun 16 15:08:06 UTC 2010


Hi Martin,
On Wed, Jun 16, 2010 at 03:24:36PM +0200, martin f krafft wrote:
> Package: kpartx
> Version: 0.4.8+git0.761c66f-8
> Severity: normal
> 
> I have three extended partitions on /dev/loop0:
> 
>   % sudo sfdisk -d /dev/loop0
>   Warning: extended partition does not start at a cylinder boundary.
>   DOS and Linux will interpret the contents differently.
>   # partition table of /dev/loop0
>   unit: sectors
> 
>   /dev/loop0p1 : start=       16, size=  7812464, Id= c
>   /dev/loop0p2 : start=  7812480, size=  3906240, Id=83, bootable
>   /dev/loop0p3 : start= 11718720, size=  3944320, Id= 5
>   /dev/loop0p4 : start=        0, size=        0, Id= 0
>   /dev/loop0p5 : start= 11718736, size=   976624, Id=83
>   /dev/loop0p6 : start= 12695376, size=   195184, Id=83
>   /dev/loop0p7 : start= 12890576, size=  2772464, Id=83
> 
> kpartx cannot handle that it seems:
> 
> % sudo kpartx -av /dev/loop0
> add map loop0p1 (253:16): 0 7812464 linear /dev/loop0 16
> add map loop0p2 (253:17): 0 3906240 linear /dev/loop0 7812480
> add map loop0p3 (253:18): 0 3944320 linear /dev/loop0 11718720
> device-mapper: resume ioctl failed: Invalid argument
> add map loop0p5 : 0 976624 linear 253:18 11718736
> device-mapper: resume ioctl failed: Invalid argument
> add map loop0p6 : 0 195184 linear 253:18 12695376
> device-mapper: resume ioctl failed: Invalid argument
> add map loop0p7 : 0 2772464 linear 253:18 12890576
> 
> % ls /dev/mapper/loop0p*
> /dev/mapper/loop0p1  /dev/mapper/loop0p2  /dev/mapper/loop0p3
> 
kpartx handles extended partitions nicely, we're using this on literally
dozenzs of servers here - although not on loop but SAN devices. 

    Is there anything in dmseg?

The ioctl fails so I think the issue is with the kernel sine the "add
map" commands all look sane or am I missing something?

    Could you check Squeeze's 2.6.32?

    Could you check if adding a map using dmsetup e.g. for loop0p7 works
    as expected?

    How exactly did you create that loop mounted file?

Cheers,
 -- Guido


> -- System Information:
> Debian Release: squeeze/sid
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.33-2-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages kpartx depends on:
> ii  dmsetup                      2:1.02.47-1 The Linux Kernel Device Mapper use
> ii  libc6                        2.11.1-2    Embedded GNU C Library: Shared lib
> ii  libdevmapper1.02.1           2:1.02.47-1 The Linux Kernel Device Mapper use
> ii  udev                         154-1       /dev/ and hotplug management daemo
> 
> kpartx recommends no packages.
> 
> kpartx suggests no packages.
> 
> -- no debconf information
> 
> 
> -- 
>  .''`.   martin f. krafft <madduck at d.o>      Related projects:
> : :'  :  proud Debian developer               http://debiansystem.info
> `. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
>   `-  Debian - when you have better things to do than fixing systems







More information about the pkg-lvm-maintainers mailing list