[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL

[Lucas Martins (oVirt JIRA)]

     [ https://ovirt-jira.atlassian.net/browse/OVIRT-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Martins updated OVIRT-1389:
---------------------------------
    Description: 
Hello, 

We are facing a big problem and our entire environment is down. 

One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). 

Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? 

  was:
Hello, 

We are facing a big problem and our entire environment is down. 

One of our POOL of disk was corrupted, so we tried to clone this pool and up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). 

Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? 


> Sanlock Error when importing a POOL 
> ------------------------------------
>
>                 Key: OVIRT-1389
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389
>             Project: oVirt - virtualization made easy
>          Issue Type: Bug
>          Components: storage
>            Reporter: Lucas Martins
>            Assignee: infra
>            Priority: Highest
>
> Hello, 
> We are facing a big problem and our entire environment is down. 
> One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). 
> Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? 



--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)