> I doubt that this can be a real solution. My guess is that glusterfsd runs > into some race condition where it locks itself up completely. > It is not funny to debug something the like on a production setup. Best would > be to have debugging output sent from the servers' glusterfsd directly to a > client to save the logs. I would not count on syslog in this case, if it > survives one could use a serial console for syslog output though. Does the system which is locking up have a fuse mountpoint? or is it a pure glusterfsd export server without a glusterfs mountpoint? Avati