Hi there, we have a big problem with our ovirt 4.1.1 enviroment. After a fc-storage failure, and an automatic reboot of the host with the hosted engine on it, we can't get the engine running again. The probelm seems an invalid lockspace. Sanlock.log shows: 2017-05-09 12:07:22+0200 35 [4991]: sanlock daemon started 3.4.0 host 360206bc-58f8-41ab-8aa9-53185222f029.kvm04.serv 2017-05-09 12:08:46+0200 119 [4996]: s1 lockspace hosted-engine:1:/var/run/vdsm/storage/920f345e-95d3-4b44-93c7-9d9931299f57/c3a02f51-6d03-4baf-908e-0c240b665714/48cfe112-b7e0-44f7-859c-d6f6c2539831:0 2017-05-09 12:09:08+0200 141 [4991]: s1 host 1 2 119 360206bc-58f8-41ab-8aa9-53185222f029.kvm04.serv Messages shows: May 9 11:38:43 kvm04 kernel: device-mapper: core: qemu-kvm: sending ioctl 5326 to DM device without required privilege. May 9 11:38:44 kvm04 sanlock[4956]: 2017-05-09 11:38:44+0200 375 [4961]: r2 cmd_acquire 2,9,12952 invalid lockspace found -1 failed 0 name 920f345e-95d3-4b44-93c7-9d9931299f57 May 9 11:38:44 kvm04 journal: Erlangen einer Sperre fehlgeschlagen: Auf dem Gerät ist kein Speicherplatz mehr verfügbar May 9 11:38:44 kvm04 journal: Ende der Datei beim Lesen von Daten: Eingabe-/Ausgabefehler May 9 11:38:44 kvm04 journal: Ende der Datei beim Lesen von Daten: Eingabe-/Ausgabefehler Manualy it is possible to mount the HE Image on the host. A filesystemcheck reports that all is clean. Also it is possible to create a file in the mounted engine image. If I remove the lockspace manuelly, it comes back within about 10 seconds. Enviroment ovirt 4.1.1 latest onn image + HE Appliance Also tested hosted-engine --reinitialize-lockspace completes without errors. Anybody any ideas? Would be very very great.... Marco