[Gluster-users] Gluster 3.2.5 client crash report

[George Machitidze]

Try EPEL repo RPM's http://fedoraproject.org/wiki/EPEL

Best regards,
George Machitidze


On Fri, Jun 29, 2012 at 12:58 PM, tungdam <lexluthor87 at gmail.com> wrote:
> Hi George
>
> On 6/29/2012 3:46 PM, George Machitidze wrote:
>
> Hi
>
> Any similarities in activities, circumstances, crash time?
>
> No, it's kind of random crashing. Run well after 10 or 12 hours and then
> crashed, without any performance degrading signature. This server is a web
> server, we have some changes 2 days ago, maybe it's making heavier I/O
> operation than before. Just let u know :)
>
>
> rpm -qa|grep -E "gluster|fuse|kernel";uname -a;cat /etc/*-release
>
> Here is info you asked:
>
> rpm -qa | grep -E "gluster|fuse|kernel"
>
> kernel-firmware-2.6.32-220.el6.noarch
> dracut-kernel-004-256.el6.noarch
> abrt-addon-kerneloops-2.0.4-14.el6.centos.x86_64
> kernel-headers-2.6.32-220.4.2.el6.x86_64
> kernel-2.6.32-220.el6.x86_64
> libreport-plugin-kerneloops-2.0.5-20.el6.x86_64
>
>  uname -a
> Linux web244 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64
> x86_64 x86_64 GNU/Linux
>
>  cat /etc/*-release
> CentOS release 6.2 (Final)
> CentOS release 6.2 (Final)
> CentOS release 6.2 (Final)
>
> lsmod | grep fuse
> fuse                   66285  3
>
> I have fuse module already, and didn't install any package from yum before,
> do i need to install it ?
>
> Many thanks
>
>
>
> Best regards,
> George Machitidze
>
>
> On Fri, Jun 29, 2012 at 12:40 PM, tungdam <lexluthor87 at gmail.com> wrote:
>
> it keep being crashed everyday.  I tried reinstalling ( from source code )
> but it didn't help, will try installing from RPM to see if it's because of
> my compiler or not. Any idea, guys ?
>
> Any help would be highly appreciated :)
>
> On 6/28/2012 8:20 AM, tungdam wrote:
>
> Hello there
>
> Our gluster client was crashed 2 times last night. The gluster partition was
> unavailable for a long time and i have to remount it manually. On the
> gluster log, i saw things like these:
>
> pending frames:
> frame : type(1) op(LOOKUP)
> frame : type(1) op(LOOKUP)
>
> patchset: git://git.gluster.com/glusterfs.git
> signal received: 11
> time of crash: 2012-06-28 00:19:24
> configuration details:
> argp 1
> backtrace 1
> dlfcn 1
> fdatasync 1
> libpthread 1
> llistxattr 1
> setfsid 1
> spinlock 1
> epoll.h 1
> xattr.h 1
> st_atim.tv_nsec 1
> package-string: glusterfs 3.2.5
> /lib64/libc.so.6[0x3cf0c32900]
>
>
> Here is my "gluster volume info" output:
>
> Volume Name: xxxxxx
> Type: Distribute
> Status: Started
> Number of Bricks: 2
> Transport-type: tcp
> Bricks:
> Brick1: Gnode1:/mnt/store
> Brick2: Gnode2:/mnt/store2
> Options Reconfigured:
> nfs.addr-namelookup: off
> nfs.rpc-auth-allow: 10.0.0.245,10.0.0.244,10.0.0.247,10.0.0.54,10.0.0.55
> auth.allow: 10.*
> cluster.min-free-disk: 5
> performance.io-thread-count: 64
> performance.cache-size: 512MB
> nfs.disable: off
> performance.write-behind-window-size: 4MB
> cluster.data-self-heal: off
> performance.stat-prefetch: off
>
> I googled around and found some people have the same problem with us but
> haven't found solution or any clues of what happened yet.  Is it a bug ? and
> if it's could you please tell me how can i overcome it ?
>
> Many thanks
>
>
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
>
>