Your message dated Sat, 30 Mar 2013 01:05:23 +0530
with message-id <[email protected]>
and subject line Re: Bug#704160: kpartx says it will create /dev/loop0p1 but
uses other names
has caused the Debian Bug report #704160,
regarding kpartx says it will create /dev/loop0p1 but uses other names
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
704160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704160
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kpartx
Version: 0.4.9+git0.4dfdaf2b-6
Severity: normal
Dear Maintainer,
I did
losetup -f /blabla/foo.img
and then
kpartx -l /dev/loop0
which told me that it was about to create /dev/loop0p1.
This sounded good so I did
kpartx -a /dev/loop0
which did not create /dev/loop0p1, but instead created
/dev/dm-6 along with vaious symlinks in /dev/disk/by-id.
The use of dm-6 makes sense from a technical point of vue, and the
symlinks in /dev/disk are fine, but please add a symlink from
/dev/loop0p1 since that's the "normal" logical name.
Stefan
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kpartx depends on:
ii dmsetup 2:1.02.74-6
ii libc6 2.13-38
ii libdevmapper1.02.1 2:1.02.74-6
ii udev 175-7.1
kpartx recommends no packages.
kpartx suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Friday 29 March 2013 07:56 PM, Stefan Monnier wrote:
>>> The use of dm-6 makes sense from a technical point of vue, and the
>>> symlinks in /dev/disk are fine, but please add a symlink from
>>> /dev/loop0p1 since that's the "normal" logical name.
>> Do you have the multipath-tools package installed ?
> I have no idea what it is so I'd guess not.
> Let me check ... no it's not installed.
>
Okay! I think I recollect it now. You will see your device's partition
listing in /dev/mapper/
That is because kpartx is part of the device mapper stack and its job is
to create device maps in the DM framework.
If you want the /dev/loop.... entries, use partx instead.
Closing bug report.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: OpenPGP digital signature
--- End Message ---
