On Sat, Sep 5, 2020 at 12:45 AM David Teigland <teigland@redhat.com> wrote:
On Sat, Sep 05, 2020 at 12:25:45AM +0300, Nir Soffer wrote:
> /var/log/sanlock.log contains a repeating: > add_lockspace > e1270474-108c-4cae-83d6-51698cffebbf:1:/dev/e1270474-108c-4cae-83d6-51698cf > febbf/ids:0 conflicts with name of list1 s1 > e1270474-108c-4cae-83d6-51698cffebbf:3:/dev/e1270474-108c-4cae-83d6-51698cf > febbf/ids:0
David, what does this message mean?
It is clear that there is a conflict, but not clear what is the conflicting item. The host id in the request is 1, and in the conflicting item, 3. No conflicting data is displayed in the error message.
The lockspace being added is already being managed by sanlock, but using host_id 3. sanlock.log should show when lockspace e1270474 with host_id 3 was added.
Do you mean that the host reporting this already joined the lockspace with host_id=3, and then tried to join again with host_id=1?