On 3/3/22, 2:57 AM, "Martin Wilck" wrote:
> I agree. kpartx is a tool for creating linear dm mappings that behave
> roughly like partitions. And it should stay that way. We (made the
> mistake to) add convenience functionality to setup loop devices when
> kpartx is called with a re
On 2/28/22, 2:44 PM, "Benjamin Marzinski" wrote:
> So unless I'm missing something, we'd only really want this for removing
> a kpartx device, in the case where somehow you have /dev/loopXpY
> partitions without the LO_FLAGS_PARTSCAN flag set on the disk. That
That's correct. We only
Ben,
Thank you for reviewing this.
On 2/22/22, 11:32 AM, "Benjamin Marzinski" wrote:
> And I'm trying to figure out why you want to create /dev/loop0p1 if you
> already have /dev/mapper/loop0p1? The ability of kpartx to create
> partitioned loop devices predates the existance "kpartx -
On 2/22/22, 10:28 AM, "Benjamin Marzinski" wrote:
On Fri, Feb 11, 2022 at 12:41:48PM -0800, Ritika Srivastava wrote:
>> Add -P, partition scanning option to kpartx which would set
>> LO_FLAGS_PARTSCAN flag during loop device creation.
>> This option
Hi,
Gentle ping
Please help review this.
--
Thanks,
Ritika
On 2/11/22, 3:51 PM, Ritika Srivastava wrote:
Add -P, partition scanning option to kpartx which would set
LO_FLAGS_PARTSCAN flag during loop device creation.
This option is same as losetup -P option
Add -P, partition scanning option to kpartx which would set
LO_FLAGS_PARTSCAN flag during loop device creation.
This option is same as losetup -P option.
Signed-off-by: Ritika Srivastava
---
kpartx/kpartx.c | 17 +
kpartx/lopart.c | 5 -
kpartx/lopart.h | 2 +-
3 files
Add -P, partition scanning option to kpartx which would set
LO_FLAGS_PARTSCAN flag during loop device creation.
This option is same as losetup -P option.
Signed-off-by: Ritika Srivastava
---
kpartx/kpartx.c | 17 +
kpartx/lopart.c | 5 -
kpartx/lopart.h | 2 +-
3 files
On 01/29/2018 03:57 PM, Martin Wilck wrote:
multipathd can't deal with other devices anyway. Proceeding further
with events for other devices just generates log noise.
Based on an idea from Ritika Srivastava .
("multipath-tools: Skip CHANGE uevent for non-mpath devices").
Change
On 01/16/2018 11:49 PM, Martin Wilck wrote:
multipathd can't deal with other devices anyway. Proceeding further
with events for other devices just generates log noise.
Based on an idea from Ritika Srivastava .
("multipath-tools: Skip CHANGE uevent for non-mpath devices").
Signed
quot;
This scenario is not actually an error and is misleading.
To fix it, the proposal is to only process the change uevent in multipath for a
multipath device.
Signed-off-by: Ritika Srivastava
---
libmultipath/uevent.c | 16
libmultipath/uevent.h | 1 +
multipathd/main.c | 8 +
10 matches
Mail list logo
