------- Comment From <email address hidden> 2015-07-30 02:13 EDT-------
(In reply to comment #19)
> Just to sum up with what has already been said.
>
> parted creates the 'p1' block device, via libparted (see dm_add_partition()
> in arch/linux.c, IIRC)
> kpartx creates the '-part1' block device (see
> /lib/udev/rules.d/*-kpartx.rules).
>
> In order to test that the '-part1' block device won't show up, you can
> disable the kpartx.rules file temporarily.
> Something like this:
> $ sudo mv /lib/udev/rules.d/*-kpartx.rules
> /lib/udev/rules.d/*-kpartx.rules.disabled
> $ sudo udevadm control --reload
>
I can confirm that after disabling kpartx by thoes commands, '-part1' block device won't show up.
------- Comment From <email address hidden> 2015-07-30 02:13 EDT------- rules.d/ *-kpartx. rules). rules.d/ *-kpartx. rules rules.d/ *-kpartx. rules.disabled
(In reply to comment #19)
> Just to sum up with what has already been said.
>
> parted creates the 'p1' block device, via libparted (see dm_add_partition()
> in arch/linux.c, IIRC)
> kpartx creates the '-part1' block device (see
> /lib/udev/
>
> In order to test that the '-part1' block device won't show up, you can
> disable the kpartx.rules file temporarily.
> Something like this:
> $ sudo mv /lib/udev/
> /lib/udev/
> $ sudo udevadm control --reload
>
I can confirm that after disabling kpartx by thoes commands, '-part1' block device won't show up.