Re: glusterfs_1.4.0qa19: small issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Indeed it did.  However, when doing multiple 10 GB dd writes on my four
> client/servers, 2 of my clients died (the other two finished their tasks
> without issue and stayed operational).  There were a large number of "frame
> :" lines in glusterfs.log, and the log ended with:
>
> frame : type(2) op(0)
> frame : type(2) op(0)
>
> 2008-06-11 20:43:20 C [common-utils.c:155:gf_print_bytes] : xfer ==
> 142359133061, rcvd == 130379872
> [0xb7fb4420]
> /lib/tls/i686/cmov/libc.so.6(abort+0x101)[0xb7e4ea01]
> /usr/lib/glusterfs/1.4.0qa19/xlator/mount/fuse.so[0xb758dd84]
> /lib/tls/i686/cmov/libpthread.so.0[0xb7f764fb]
> /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0xb7ef8e5e]
> ---------
>

did the client memory usage grow very high before it crashed? can you tell
us the size of the core dump file? also is it possible to get a gdb
backtrace on the coredump? this will help us a lot.

thanks!
avati


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux