[ovirt-users] engine.log is looping with Volume XXX contains a apparently corrupt brick(s).

[Nico]

Le 2015-10-12 14:04, Nir Soffer a écrit : 

> Yes, engine will let you use such volume in 3.5 - this is a bug. In 3.6 you will
> not be able to use such setup.
> 
> replica 2 fails in a very bad way when one brick is down; the
> application may get
> stale data, and this breaks sanlock. You will be get stuck with spm
> that cannot be
> stopped and other fun stuff.
> 
> You don't want to go in this direction, and we will not be able to support that.
> 
>> here the last entries of vdsm.log
> 
> We need the whole file.
> 
> I suggest you file an ovirt bug and attach the full vdsm log file
> showing the timeframe of
> the error. Probably from the time you created the glusterfs domain.
> 
> Nir

Please find the full logs there: 

https://94.23.2.63/log_vdsm/vdsm.log [1] 

https://94.23.2.63/log_vdsm/ [2] 

https://94.23.2.63/log_engine/ [3] 

 

Links:
------
[1] https://94.23.2.63/log_vdsm/vdsm.log
[2] https://94.23.2.63/log_vdsm/
[3] https://94.23.2.63/log_engine/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20151012/437b68d5/attachment-0001.html>