fstab mount option for devices created on top of LUKS devices
Blacklisting with partition devices:
When the device name is listed as /dev/sdb1 ( for example ), blacklisting was trying to do 'multipath -a /dev/sdb1'
Now with regex pattern in the play, even with input device as /dev/sdb1, blacklisting will try 'multipath -a /dev/sdb'
fstab mount option for devices created on top of LUKS devices:
When using device name corresponding to LUKS device ( /dev/mapper/luks_sdc ), and enabling VDO on that
brick, adds the VDO options for all the bricks, as the earlier logic always considered whatever as '/dev/mapper/'
as VDO device. Now LUKS device is also created under '/dev/mapper' and that is considered as VDO device
as per that logic. Latest logic includes searching for VDO devices with patter '/dev/mapper/vdo', rather than
simple search of '/dev/mapper/
This PR fixes 2 issues
Blacklisting with partition devices: When the device name is listed as /dev/sdb1 ( for example ), blacklisting was trying to do 'multipath -a /dev/sdb1' Now with regex pattern in the play, even with input device as /dev/sdb1, blacklisting will try 'multipath -a /dev/sdb'
fstab mount option for devices created on top of LUKS devices: When using device name corresponding to LUKS device ( /dev/mapper/luks_sdc ), and enabling VDO on that brick, adds the VDO options for all the bricks, as the earlier logic always considered whatever as '/dev/mapper/' as VDO device. Now LUKS device is also created under '/dev/mapper' and that is considered as VDO device as per that logic. Latest logic includes searching for VDO devices with patter '/dev/mapper/vdo', rather than simple search of '/dev/mapper/