Your message dated Wed, 27 Dec 2017 11:22:50 +0530
with message-id <[email protected]>
and subject line Re: Bug#884791: kpartx incompatible with loop.max_part
has caused the Debian Bug report #884791,
regarding kpartx incompatible with loop.max_part
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.)
--
884791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884791
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kpartx
Version: 0.6.4-5+b1
Severity: normal
Dear maintainer,
There is a problem with the current version of kpartx in Debian,
which is probably fixed upstream by commit 6ff376d43cadf934447,
released in version 0.7.2.
Having inserted the 'loop' module with option max_part=8
(modprobe loop max_part=8), a simple invocation of vmdeboostrap (1.8-1)
to create a disk image with one partition fails because of kpartx:
# vmdebootstrap --verbose --image=vmd1 --size=1G --arch=i386 --grub
Creating disk image
Creating partitions
EEEK! Something bad happened...
command failed: ['kpartx', '-avs', 'vmd1']
[...]
indeed, the kernel already created loop1p1, and kpartx is confused by
this situation, as it identifies that loop1p1 is the loop device
attached to vmd1, instead of loop1:
# kpartx -avs vmd1
device-mapper: reload ioctl on loop1p1p1 failed: Device or resource busy
create/reload failed on loop1p1p1
# kpartx -l vmd1
loop1p1p1 : 0 1949693 /dev/loop1p1 3
Not using the loop's max_part option can workaround the issue.
The upstream commit will probably cause kpartx to identify loop1 as
the correct loop device and overwrite loop1p1, working around the
problem.
-- System Information:
Debian Release: buster/sid
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages kpartx depends on:
ii dmsetup 2:1.02.145-4.1
ii libc6 2.25-5
ii libdevmapper1.02.1 2:1.02.145-4.1
ii udev 236-1
kpartx recommends no packages.
kpartx suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 2017-12-19 at 20:04 +0100, Nicolas Cavallari wrote:
> There is a problem with the current version of kpartx in Debian,
> which is probably fixed upstream by commit 6ff376d43cadf934447,
> released in version 0.7.2.
I haven't verified but since you've mentioned the version where the fix
is included, this should be fixed with the latest 0.7.4 upload
Thanks.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
--- End Message ---
