[Gluster-users] 32bit client and 64bit server.

Mike Terzo mterzo at gmail.com
Fri Feb 26 22:22:32 UTC 2010

I found this in the archives:

I don't see any follow ups with any sort of solution. I'm running
gluster 3.0.2 with patch 2659 with a 64bit client and 64bit server
without any issues.  I turned up another box running 32 bit client
pointing to 2 different 64bit servers and I had the same issues listed
above. My kernels on both boxes clients are 2.6.30 neither have any
patches applied.

Here's my client output

pending frames:
frame : type(1) op(LOOKUP)
frame : type(1) op(STAT)
frame : type(1) op(STAT)

patchset: v3.0.2
signal received: 11
time of crash: 2010-02-26 16:01:08
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.0.2
Segmentation fault (core dumped)

I've turned off io-threads and the process hasn't cored again.  Is
this a general practice to not mix 32bit client and 64bit servers?

--mike terzo

More information about the Gluster-users mailing list