Bug#704160: kpartx says it will create /dev/loop0p1 but uses other names

[Ritesh Raj Sarraf]

On Fri, 2013-03-29 at 20:53 -0400, Stefan Monnier wrote:
> >> I suggested to fix it by adding a /dev/loop0p1 symlink,
> > Why? That part is anyways taken care by partx.
> 
> So maybe the problem is in partx.  I must say I don't know what's the
> relationship between partx and kpartx.  All I know is that the 
> "loop0p1"
> mentioned in the output of "kpartx -l" (made a lot of sense and) 
> created
> for me the expectation to find a /dev/loop0p1.  Instead I had to look 
> by
> hand for some symlink in /dev/disk to figure out which name can be 
> used.

Hello Stefan,


How are you ? Time flies. I did not realize that this bug report is
from 2013. :-)


I was doing the periodical refresh of multipath-tools and dug up on
your bug report.

While I agree that the output of `kpartx -l` makes it look obvious that
the device mentioned resides in /dev/.

But I think this is well covered in the man page. Quoting it...

EXAMPLE
       To mount all the partitions in a raw disk image:

              kpartx -av disk.img

       This will output lines such as:

              loop3p1 : 0 20964762 /dev/loop3 63

       The loop3p1 is the name of a device file under  /dev/mapper 
 which  you
       can use to access the partition, for example to fsck it:

              fsck /dev/mapper/loop3p1

       When you're done, you need to remove the devices:

              kpartx -d disk.img


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20150809/8a5206c5/attachment-0001.sig>