ph-users@lists.ceph.com
Betreff: Re: [ceph-users] TCMU Runner: Could not check lock ownership. Error:
Cannot send after transport endpoint shutdown
- Each LUN is exported to multiple clients (at the same time)
- yes, IO is done to the LUNs (read and write); (oVirt runs VMs on each of the
LUNs)
lian Ries; ceph-users@lists.ceph.com
> *Betreff:* Re: [ceph-users] TCMU Runner: Could not check lock ownership.
> Error: Cannot send after transport endpoint shutdown
>
> On 10/22/2019 03:20 AM, Kilian Ries wrote:
>> Hi,
>>
>>
>> i'm running a ceph cluster with 4x
2019 19:43:40
An: Kilian Ries; ceph-users@lists.ceph.com
Betreff: Re: [ceph-users] TCMU Runner: Could not check lock ownership. Error:
Cannot send after transport endpoint shutdown
On 10/22/2019 03:20 AM, Kilian Ries wrote:
> Hi,
>
>
> i'm running a ceph cluster with 4x ISCSI ex
On 10/22/2019 03:20 AM, Kilian Ries wrote:
> Hi,
>
>
> i'm running a ceph cluster with 4x ISCSI exporter nodes and oVirt on the
> client side. In the tcmu-runner logs i the the following happening every
> few seconds:
>
>
Are you exporting a LUN to one client or multiple clients at the same
Hi,
i'm running a ceph cluster with 4x ISCSI exporter nodes and oVirt on the client
side. In the tcmu-runner logs i the the following happening every few seconds:
###
2019-10-22 10:11:11.231 1710 [WARN] tcmu_rbd_lock:762 rbd/image.lun0: Acquired
exclusive lock.
2019-10-22 10:11:11.395 1710
