Anand Avati <anand.avati@xxxxxxxxx> wrote: > What operations were you performing which lead to this? I made progress. Things go haywire because the system runs out of memory. And it runs out of memory because glusterfs never replies to some FUSE SETATTR. The requests queue in memory until it explodes. The issue happens on specific files. Once I added debug output I have been able to spot them, and to reproduce the problem from the shell: $ touch share/mk/bsd.sys.mk (waits forever until I hit ^C) Restarting glusterfs bricks fixed this problem. Let us see if I can reproduce it... -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
