[Gluster-users] Gluster (2.0.1 -> git) with fuse 2.8 crashes NFS

[Harshavardhana]

Hi Justice,

     Can you get a backtrace from the segfault through gdb? .

Regards
--
Harshavardhana
Z Research Inc http://www.zresearch.com/


On Sat, Jun 20, 2009 at 10:47 PM, <jlondon at lawinfo.com> wrote:

> Sure, the kernel version is 2.6.29 and the fuse release is the just
> released 2.8.0-pre3 (although I can use pre2 if needed).
>
> Justice London
> jlondon at lawinfo.com
>
> > Hi Justice,
> >
> >      There are certain modifications required in fuse-extra.c to make
> > glusterfs work properly for fuse 2.8.0 release. glusterfs 2.0.1 release
> is
> > not tested against 2.8.0 release fuse and certainly will not work without
> > those modifications.  May i know the kernel version you are trying to
> use?
> > and the version of fuse being under use? pre1 or pre2 release?
> >
> > Regards
> > --
> > Harshavardhana
> > Z Research Inc http://www.zresearch.com/
> >
> >
> > On Fri, Jun 19, 2009 at 11:14 PM, Justice London
> > <jlondon at lawinfo.com>wrote:
> >
> >>  No matter what I do I cannot seem to get gluster to stay stable when
> >> doing any sort of writes to the mount, when using gluster in combination
> >> with fuse 2.8.0-preX and NFS. I tried both unfs3 and standard kernel-nfs
> >> and
> >> no matter what, any sort of data transaction seems to crash gluster
> >> immediately. The error log is as such:
> >>
> >>
> >>
> >> pending frames:
> >>
> >>
> >>
> >> patchset: git://git.sv.gnu.org/gluster.git
> >>
> >> signal received: 11
> >>
> >> configuration details:argp 1
> >>
> >> backtrace 1
> >>
> >> bdb->cursor->get 1
> >>
> >> db.h 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 2.0.0git
> >>
> >> [0xf57fe400]
> >>
> >> /usr/local/lib/libglusterfs.so.0(default_fxattrop+0xc0)[0xb7f4d530]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/xlator/protocol/server.so(server_fxattrop+0x175)[0xb7565af5]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/xlator/protocol/server.so(protocol_server_interpret+0xbb)[0xb755beeb]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/xlator/protocol/server.so(protocol_server_pollin+0x9c)[0xb755c19c]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/xlator/protocol/server.so(notify+0x7f)[0xb755c21f]
> >>
> >> /usr/local/lib/libglusterfs.so.0(xlator_notify+0x3f)[0xb7f4937f]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/transport/socket.so(socket_event_poll_in+0x3d)[0xb4d528dd]
> >>
> >>
> >>
> /usr/local/lib/glusterfs/2.0.0git/transport/socket.so(socket_event_handler+0xab)[0xb4d5299b]
> >>
> >> /usr/local/lib/libglusterfs.so.0[0xb7f6321a]
> >>
> >> /usr/local/lib/libglusterfs.so.0(event_dispatch+0x21)[0xb7f62001]
> >>
> >> /usr/local/sbin/glusterfsd(main+0xb3b)[0x804b81b]
> >>
> >> /lib/libc.so.6(__libc_start_main+0xe5)[0xb7df3455]
> >>
> >> /usr/local/sbin/glusterfsd[0x8049db1]
> >>
> >>
> >>
> >> Any ideas on if there is a solution, or will be one upcoming in either
> >> gluster or fuse?  Other than with NFS, the git version of gluster seems
> >> to
> >> be really, really fast with fuse 2.8
> >>
> >>
> >>
> >> Justice London
> >> jlondon at lawinfo.com
> >>
> >>
> >>
> >> _______________________________________________
> >> Gluster-users mailing list
> >> Gluster-users at gluster.org
> >> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
> >>
> >>
> >
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090622/e1267ab7/attachment.html>