guration?
> The process must have dumped a core file. Could you attach the core to gdb
> and provide its backtrace as well?
>
> -Krutika
>
> --
>
> *From: *"Mathieu Chateau"
> *To: *"gluster-users"
> *Sent: *Wednesday, Jun
rom: "Mathieu Chateau"
> To: "gluster-users"
> Sent: Wednesday, June 17, 2015 7:16:03 PM
> Subject: [Gluster-users] gluster client crash
> Hello,
> On on my gluster mount crashed this morning on one of my gluster client for
> this share.
> I am use fuse.
&g
Hello,
On on my gluster mount crashed this morning on one of my gluster client for
this share.
I am use fuse.
Gluster server wad updated to 3.7.1 and this client too but not rebooted.
Trying to mount again this share failed. After reboot, everything is ok
again.
Any clue ?
Jun 17 07:57:32 mycli
sorry, our customer remounted, so it is possible to get the full backtrace.
the full version is glusterfs-3.3.0.5rhs_iqiyi_6-1.el6.x86_64
it is a self-built version.
The code started from this change.
%changelog
* Wed May 9 2012 Kaleb S. KEITHLEY
- Add BuildRequires: libxml2-devel so that config
On 01/27/2014 01:34 PM, Mingfan Lu wrote:
the volume is distributed (replication = 1)
Is it possible to obtain a full backtrace using gdb?
Also, what is the complete version string of this glusterfs release?
Thanks,
Vijay
On Mon, Jan 27, 2014 at 4:01 PM, Mingfan Lu mailto:mingfan...@gmail
the volume is distributed (replication = 1)
On Mon, Jan 27, 2014 at 4:01 PM, Mingfan Lu wrote:
> One of our client (3.3.0.5) crashed when writing data, the log is:
>
> pending frames:
> frame : type(1) op(WRITE)
> frame : type(1) op(WRITE)
> frame : type(1) op(WRITE)
> frame : type(1) op(WRITE)
One of our client (3.3.0.5) crashed when writing data, the log is:
pending frames:
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame : type(1) op(WRITE)
frame :
