[SPDK] Re: is it possible to add a blacklist for the lvol module?

My project could take care of the ownership, so "claim" is not really
required (although "claim" is still a good to have feature). Currently
does SPDK has any way to disable "claim"?
By the way, I don't write my SPDK application, I use the
"app/spdk_tgt/spdk_tgt" as a part of my project. So I hope I could
operate it via RPC.

Best regards.

On Wed, Apr 1, 2020 at 6:13 AM Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com> wrote:
>
> On Mon, Mar 30, 2020, 21:56 peng yu <yupeng0921(a)gmail.com> wrote:
>
> > I have a below scenario:
> > A disk is controlled by SPDK APP A.
> > SPDK APP A exports the disk as a NVMEoF target
> > SPDK APP B is a NVMEoF initiator, it connects to that disk.
> > SPDk APP B creates a lvs and a lvol on the disk.
> > When I restart the APP A and APP B. The APP A will examine the disk
> > and find there is a lvs, and then the lvol module on APP A will claim
> > this disk, then this disk can't be exported over NVMEoF.
> >
> > Could we add a api to the lvol module? The api could add a dev name
> > pattern to a black list. When the lvol module examine a disk, it will
> > check against the black list, if a dev name matches the black list, it
> > will ignore this device.
> >
>
> There's another option to check out here: is there any need in your
> scenario for the lvol module and nvmf target to claim the lvol? Basically,
> claims ensure single bdev owner which, outside fool-proofing and/or
> hardware with special requirements, isn't strictly necessary (provided your
> apps take care of the ownership).
>
> Regards,
> Andrey
>
> >
> > Best regards.
> > _______________________________________________
> > SPDK mailing list -- spdk(a)lists.01.org
> > To unsubscribe send an email to spdk-leave(a)lists.01.org
> >
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org