On 12/06/2014, at 6:58 AM, Niels de Vos wrote:
snip
If you capture a vmcore (needs kdump installed and configured), we may
be able to see the cause more clearly.
That does help, and so will Harsha's suggestion too probably. :)
I'll look into it properly later on today.
For the moment, I've
On Thu, Jun 12, 2014 at 07:26:25AM +0100, Justin Clift wrote:
On 12/06/2014, at 6:58 AM, Niels de Vos wrote:
snip
If you capture a vmcore (needs kdump installed and configured), we may
be able to see the cause more clearly.
Oh, these seem to be Xen hosts. I don't think kdump (mainly kexec)
Hi Niels,
4 out of 5 Rackspace slave VM's hung overnight. Rebooted one of
them and it didn't come back. Checking out it's console (they
have an in-browser Java applet for it) showed a kernel traceback.
Scrollback for the console (took some effort ;) is attached.
It's showing a bunch of XFS
This doesn't look like xfs bug. It is likely caused by a bad disk /
array or a really busy host.
On Wed, Jun 11, 2014 at 10:28 PM, Justin Clift jus...@gluster.org wrote:
Hi Niels,
4 out of 5 Rackspace slave VM's hung overnight. Rebooted one of
them and it didn't come back. Checking out it's
Thanks. :)
Going to assume really busy host. (hoping)
I guess looking into raising the timeout value or something would be
the right thing to try first. I'll look into it after getting some
sleep in a bit.
+ Justin
On 12/06/2014, at 6:47 AM, Anand Babu Periasamy wrote:
This doesn't look
On Thu, Jun 12, 2014 at 06:28:13AM +0100, Justin Clift wrote:
Hi Niels,
4 out of 5 Rackspace slave VM's hung overnight. Rebooted one of
them and it didn't come back. Checking out it's console (they
have an in-browser Java applet for it) showed a kernel traceback.
Scrollback for the
