Re: [Users] Storage unresponsive after sanlock

2014-01-29 Thread Maor Lipchuk
The VDSM log seems to be from the 26th and from the engine logs it seems that the incident occurred at the 24th, so I can't really see the what happened in VDSM that time. From the engine logs it seems that at around 2014-01-24 16:59 the master storage domain was in maintenance and then there was

Re: [Users] Storage unresponsive after sanlock

2014-01-29 Thread Trey Dockendorf
On Wed, Jan 29, 2014 at 4:33 AM, Maor Lipchuk mlipc...@redhat.com wrote: The VDSM log seems to be from the 26th and from the engine logs it seems that the incident occurred at the 24th, so I can't really see the what happened in VDSM that time. From the engine logs it seems that at around

Re: [Users] Storage unresponsive after sanlock

2014-01-29 Thread Trey Dockendorf
On Wed, Jan 29, 2014 at 4:33 AM, Maor Lipchuk mlipc...@redhat.com wrote: The VDSM log seems to be from the 26th and from the engine logs it seems that the incident occurred at the 24th, so I can't really see the what happened in VDSM that time. From the engine logs it seems that at around

Re: [Users] Storage unresponsive after sanlock

2014-01-28 Thread Maor Lipchuk
Hi Trey, Can you please also attach the engine/vdsm logs. Thanks, Maor On 01/27/2014 06:12 PM, Trey Dockendorf wrote: I setup my first oVirt instance since 3.0 a few days ago and it went very well, and I left the single host cluster running with 1 VM over the weekend. Today I come back and

[Users] Storage unresponsive after sanlock

2014-01-27 Thread Trey Dockendorf
I setup my first oVirt instance since 3.0 a few days ago and it went very well, and I left the single host cluster running with 1 VM over the weekend. Today I come back and the primary data storage is marked as unresponsive. The logs are full of entries [1] that look very similar to a knowledge