Re: [Users] VM crashes and doesn't recover
----- Original Message -----
From: "Yuval M" <yuvalme(a)gmail.com>
To: "Dan Kenigsberg" <danken(a)redhat.com>
Cc: users(a)ovirt.org, "Nezer Zaidenberg" <nzaidenberg(a)mac.com>
Sent: Friday, March 29, 2013 2:19:43 PM
Subject: Re: [Users] VM crashes and doesn't recover
Any ideas on what can cause that storage crash?
could it be related to using a SSD?
What the logs say is that the IO on the storage domain are failing (both
the oop timeouts and the sanlock log) and this triggers the VDSM restart.
On Sun, Mar 24, 2013 at 09:50:02PM +0200, Yuval M wrote:
> I am running vdsm from packages as my interest is in developing for the
> I noticed that when the storage domain crashes I can't even do "df
-h"
> (hangs)
This is also consistent with the unreachable domain.
The dmesg log that you attached doesn't contain timestamps so it's hard to
correlate with the rest.
If you want you can try to reproduce the issue and resubmit the logs:
/var/log/vdsm/vdsm.log
/var/log/sanlock.log
/var/log/messages
(Maybe stating also the exact time when the issue begins to appear)
In the logs I noticed that you're using only one NFS domain, and I think that
the SSD (on the storage side) shouldn't be a problem. When you experience such
failure are you able to read/write from/to the SSD on machine that is serving
the share? (If it's the same machine check that using the "real" path where
it's mounted, not the nfs share)
--
Federico