>
> >
> > My use case would be a HA cluster where a VM is mapping an rbd image,
> and then it encounters some network issue. An other node of the HA
> cluster could start the VM and map again the image, but if the
> networking is fixed on the first VM that would keep using the already
> mapped ima
On Fri, Mar 25, 2022 at 4:11 PM Ilya Dryomov wrote:
>
> On Thu, Mar 24, 2022 at 2:04 PM Budai Laszlo wrote:
> >
> > Hi Ilya,
> >
> > Thank you for your answer!
> >
> > On 3/24/22 14:09, Ilya Dryomov wrote:
> >
> >
> > How can we see whether a lock is exclusive or shared? the rbd lock ls
> > comm
On Thu, Mar 24, 2022 at 2:04 PM Budai Laszlo wrote:
>
> Hi Ilya,
>
> Thank you for your answer!
>
> On 3/24/22 14:09, Ilya Dryomov wrote:
>
>
> How can we see whether a lock is exclusive or shared? the rbd lock ls command
> output looks identical for the two cases.
>
> You can't. The way --exclu
Hi Ilya,
Thank you for your answer!
On 3/24/22 14:09, Ilya Dryomov wrote:
How can we see whether a lock is exclusive or shared? the rbd lock ls command
output looks identical for the two cases.
You can't. The way --exclusive is implemented is the client simply
refuses to release the lock w
On Thu, Mar 24, 2022 at 11:06 AM Budai Laszlo wrote:
>
> Hi all,
>
> is there any possibility to turn an exclusive lock into a shared one?
>
> for instance if I map a device with "rbd map testimg --exclusive" then is
> there any way to switch that lock to a shared one so I can map the rbd image
