[dm-devel] [PATCH] multipathd: deferred device adding

Gioh Kim gi-oh.kim at profitbricks.com
Thu Nov 10 15:54:04 UTC 2016


On 10.11.2016 16:19, Hannes Reinecke wrote:
> On 11/10/2016 04:05 PM, Gioh Kim wrote:
>> Current multipathd always receives events from udev
>> and add devices to topology immediately. For example,
>> if sdb is added, multipathd receives the event from sdb
>> and add sdb into the topology.
>> But some platform needs to defer adding new device
>> until user adds device manually, for instance, with "multipathd add sdb".
>>
>> I tested this patch to disable ueventloop.
>> There was no problem on my platform.
>>
>> Is there a configuration for multipath.conf or udev rule
>> for deferred device adding?
>> Or what about adding new configuration for that?
>>
>> Signed-off-by: Gioh Kim <gi-oh.kim at profitbricks.com>
>> ---
>>  multipathd/main.c | 6 ++++--
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>>
> Please elaborate.
>
> Which platforms would be needing that?
>
> Cheers,
>
> Hannes

Hi Hannes,

I thank you for the response.

The platform is the custom platform based on debian jessie distribution.

And new sdX device is created when the remote storage volume is connected via SCST.

I don't want to create a dm device when sdX is created because there are other jobs before export the volume.

For example, I need to change the size or format or copy data into sdb.

I want to create the dm device when I finished the setup.

I could disabled the socket in multipath udev rule file with v0.4.9.
But I cannot find a way to ignore the uevent.


-- 
Best regards,
Gioh Kim
TEL: 0176 2697 8962




More information about the dm-devel mailing list