Ok, I tried the debug once before, must have missed it. I did see dome
errors on the client side, but not the server side. Here is the log
excert:
2007-10-22 00:19:07 D [inode.c:351:__active_inode] fuse/inode: activating
inode(16750137), lru=1/1024
2007-10-22 00:19:07 D [fuse-bridge.c:423:fuse_lookup] glusterfs-fuse:
LOOKUP 16750137/1193026747.V19Iffa3a9M917884.anubis.mydomain.com
(/mydomain.com/webmaster/new/1193026747.V19Iffa3a9M917884.anubis.mydomain.com)
2007-10-22 00:19:07 D [fuse-bridge.c:378:fuse_entry_cbk] glusterfs-fuse:
ERR => -1 (2)
2007-10-22 00:19:07 D [inode.c:308:__destroy_inode] fuse/inode: destroy
inode(0) address@hidden
2007-10-22 00:19:07 D [inode.c:381:__passive_inode] fuse/inode:
passivating inode(16750137), lru=2/1024
2007-10-22 00:19:07 D [inode.c:351:__active_inode] fuse/inode: activating
inode(16753577), lru=1/1024
2007-10-22 00:19:07 D [inode.c:351:__active_inode] fuse/inode: activating
inode(16750137), lru=0/1024
2007-10-22 00:19:07 D [fuse-bridge.c:1052:fuse_link] glusterfs-fuse: LINK
/mydomain.com/webmaster/tmp/1193026747.P24588.anubis.mydomain.com
/mydomain.com/webmaster/new/1193026747.V19Iffa3a9M917884.anubis.mydomain.com
2007-10-22 00:19:07 D [fuse-bridge.c:346:fuse_entry_cbk] glusterfs-fuse:
ENTRY => 16753577
2007-10-22 00:19:07 D [inode.c:381:__passive_inode] fuse/inode:
passivating inode(16753577), lru=1/1024
2007-10-22 00:19:07 D [fuse-bridge.c:917:fuse_unlink] glusterfs-fuse:
UNLINK 16750136/1193026747.P24588.anubis.mydomain.com
The client and server run fine without crashing, so I really couldn't
backtrace it (or could I?)
I tried to find the tla release you mentioned, I am not sure which one to
use, do you have a direct link I could use?