[Gluster-users] QEMU gfapi segfault

[Josh Boon]

Not this time around. I've increased the limits as these machines are rather big for ram requirements. 
----- Original Message -----
From: "Vijay Bellur" <vbellur at redhat.com>
To: "Josh Boon" <gluster at joshboon.com>, "Gluster-users at gluster.org List" <gluster-users at gluster.org>
Sent: Wednesday, December 31, 2014 4:06:09 PM
Subject: Re: [Gluster-users] QEMU gfapi segfault

On 12/31/2014 04:11 AM, Josh Boon wrote:
> Hey folks,
>
> I'm working on tracking down rogue QEMU segfaults in my infrastructure
> that look to be dying due to gluster. The tips that I get is that the
> process is in disk sleep when it dies and the process is backed only by
> gluster and the segfault lends to io system issues. Unfortunately I
> haven't figured out how to get a full crash dump so I can run it through
> apport-retrace to get exactly what went wrong. The other interesting
> thing is this happens only when gluster is under heavy load. Any tips
> about debugging further or getting this fixed up would be appreciated.
>
> Segfault:
>
> Dec 30 20:42:56 HFMHVR3 kernel: [5976247.820875] qemu-system-x86[27730]:
> segfault at 128 ip 00007f891f0cc82c sp 00007f89376846a0 error 4 in
> qemu-system-x86_64 (deleted)[7f891ed42000+4af000]
>

Do you see a qemu core dump file? If yes, can you please post the backtrace?

-Vijay