Shehjar Tikoo schrieb: >> >> the last lines of the serverlog were: >>> pending frames: >>> frame : type(1) op(UNLINK) >>> frame : type(1) op(UNLINK) >>> >>> patchset: 7b2e459db65edd302aa12476bc73b3b7a17b1410 >>> signal received: 11 >>> configuration details:db.h 1 >>> dlfcn 1 >>> libpthread 1 >>> spinlock 1 >>> extattr.h 1 >>> st_atimespec.tv_nsec 1 >>> package-string: glusterfs 2.0.0 >>> > > There has to be a stack-trace following the lines above in the log. > Please paste the stack trace also. The full log below doest not have > it either. > > -Shehjar > Thanks for you reply. But I'm sorry to say, that there isn't a stack trace to paste. I've made another run and the logfiles just shows > pending frames: > frame : type(1) op(UNLINK) > > patchset: 7b2e459db65edd302aa12476bc73b3b7a17b1410 > signal received: 11 > configuration details:db.h 1 > dlfcn 1 > libpthread 1 > spinlock 1 > extattr.h 1 > st_atimespec.tv_nsec 1 > package-string: glusterfs 2.0.0 > 2009-05-08 15:00:19 D [glusterfsd.c:339:_get_specfp] glusterfs: > loading volume file > /usr/local/etc/glusterfs/new_glusterfs_server_justhome.vol > ================================================================================ > Version : glusterfs 2.0.0 built on May 1 2009 19:24:54 > [...] But i've search and found a glusterfsd.core in / http://www.physik.tu-berlin.de/~frendor/glusterfs/glusterfsd.core It's binary data, but maybe it helps. Can i do something to get the stack-trace? I've configured and build glusterfs with the parameters: > export LDFLAGS="-L/usr/local/lib -liconv" > export CFLAGS="-O0 -g -DDEBUG -I/usr/local/include/" > ./configure the -DDEBUG should give some more output. Additionaly i've started glusterfs with > -L DEBUG Thanks Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: <http://zresearch.com/pipermail/gluster-users/attachments/20090508/5f5a79ee/attachment.pgp>
