Hello Krishna,
Can you reproduce the bug?? I have made more test about this issue, I comment you my impressions: * The bug happens when the client (that goes down) tries a write operation over the GlusterFS (cp local glusterfs) and the other client tries an ls command or and find /mnt/glusterfs -type f -print0 | xargs -0 head -c1 >/dev/null command. With other commands I dont be able to reproduce the bug. * I dont be able to reproduce the bug with a read operation in the client that goes down. Only write operations (cp local glusterf). * I can see that some times when I try to reproduce the bug (with a write operation) the bug not happens, I dont know the reason. The majority of times the bug is reproduced. * I test with a schema without unify translator, in place this I use the stripe translator; Im be able to reproduce the same bug with this configuration too. I hope that these points help you to clarify the problem. Thanks. _______________________________________________ Gluster-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gluster-devel
