Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-04 Thread InterNetX - Juergen Gotteswinter
Am 6/3/2016 um 6:37 PM schrieb Nir Soffer: > On Fri, Jun 3, 2016 at 11:27 AM, InterNetX - Juergen Gotteswinter > wrote: >> What if we move all vm off the lun which causes this error, drop the lun >> and recreated it. Will we "migrate" the error with the VM to a

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-03 Thread Nir Soffer
On Fri, Jun 3, 2016 at 11:27 AM, InterNetX - Juergen Gotteswinter wrote: > What if we move all vm off the lun which causes this error, drop the lun > and recreated it. Will we "migrate" the error with the VM to a different > lun or could this be a fix? This

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-03 Thread InterNetX - Juergen Gotteswinter
What if we move all vm off the lun which causes this error, drop the lun and recreated it. Will we "migrate" the error with the VM to a different lun or could this be a fix? Am 6/3/2016 um 10:08 AM schrieb InterNetX - Juergen Gotteswinter: > Hello David, > > thanks for your explanation of those

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-03 Thread InterNetX - Juergen Gotteswinter
Hello David, thanks for your explanation of those messages, is there any possibility to get rid of this? i already figured out that it might be an corruption of the ids file, but i didnt find anything about re-creating or other solutions to fix this. Imho this occoured after an outage where

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-02 Thread David Teigland
On Thu, Jun 02, 2016 at 06:47:37PM +0300, Nir Soffer wrote: > > This is a mess that's been caused by improper use of storage, and various > > sanity checks in sanlock have all reported errors for "impossible" > > conditions indicating that something catastrophic has been done to the > > storage

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-02 Thread Nir Soffer
On Thu, Jun 2, 2016 at 6:35 PM, David Teigland wrote: >> verify_leader 2 wrong space name >> 4643f652-8014-4951-8a1a-02af41e67d08 >> f757b127-a951-4fa9-bf90-81180c0702e6 >> /dev/f757b127-a951-4fa9-bf90-81180c0702e6/ids > >> leader1 delta_acquire_begin error -226 lockspace >>

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-02 Thread David Teigland
> verify_leader 2 wrong space name > 4643f652-8014-4951-8a1a-02af41e67d08 > f757b127-a951-4fa9-bf90-81180c0702e6 > /dev/f757b127-a951-4fa9-bf90-81180c0702e6/ids > leader1 delta_acquire_begin error -226 lockspace > f757b127-a951-4fa9-bf90-81180c0702e6 host_id 2 VDSM has tried to join

Re: [ovirt-users] Sanlock add Lockspace Errors

2016-06-02 Thread Nir Soffer
On Mon, May 30, 2016 at 11:06 AM, InterNetX - Juergen Gotteswinter wrote: > Hi, > > since some time we get Error Messages from Sanlock, and so far i was not > able to figure out what exactly they try to tell and more important if > its something which can be ignored or needs

[ovirt-users] Sanlock add Lockspace Errors

2016-05-30 Thread InterNetX - Juergen Gotteswinter
Hi, since some time we get Error Messages from Sanlock, and so far i was not able to figure out what exactly they try to tell and more important if its something which can be ignored or needs to be fixed (and how). Here are the Versions we are using currently: Engine