[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] [Patch] kpartx to accept device map name



Hi,

Excuse me for the misleading message.

The problem I saw was that when executing kpartx just after
multipath (in shell script), kpartx was invoked too early
and couldn't see the device node. I could avoid it by
inserting "sleep 5" after multipath execution but I can't
tell whether it's enough.
Kiyoshi's patch should fix it and the device node will be
created on the location which libdevmapper knows. (/dev/mapper)

'-m' option provides a way to avoid dependency to hidden knowledge
about the location (/dev or /dev/mapper or anywhere else).
Without this, we have to synchronize udev rules, hotplug shell
scripts and initscripts to see the same device node for dm devices.
This is why I thought it's better to give kpartx an option like this.

..However, in the really latest CVS, dmsetup has a new function
to execute external command with device node name.
So we can do the same thing with dmsetup now.
Given that you are reluctant to add kpartx more relationship with
libdevmapper, dmsetup is the best place.

Thanks,
Jun'ichi Nomura

christophe varoqui wrote:
> Can you elaborate on the problems you see with the asynchronous hotplug
> model ?
> 
> I would like to express my reluctance to add a devmap special case to
> kpartx.
> 
> On lun, 2005-05-16 at 15:21 -0400, Jun'ichi Nomura wrote:
>>Attached patch adds '-m' option which makes kpartx
>>to accept device map name.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]