Amar, Your comment is about the log flooding, isn't it? But what about the first part of my message - "ls /glusterfs_volume" hang, when executed just after node disconnection? Have you reproduced this issue? Previously in the tla772, "ls /glusterfs_volume" have been failing more gently, just with the "Transport endpoint is not connected" message... :) Regards, Andrey 2008/6/19 Amar S. Tumballi <amar@xxxxxxxxxxxxx>: > NovA, > Another valid point, which was in our todo from long time. Will be done > soon. > >> >> 2008/6/18 Amar S. Tumballi <amar@xxxxxxxxxxxxx>: >>> The fix for this issue is in the source repo now. You can try out >>> beating it hard again. Let me know about the problems if you have any. >> Oh, what a fast response! :) Thanks a lot! >> Unify is working now as expected. But not without problems, >> unfortunately... >> >> When I disconnect one of the node and do "ls /home" at once, the >> command hangs and can't be killed even with SIGKILL. The client log >> contains: >> ------ >> ... skipped ... >> ------ >> >> But after some time (seemingly concerned with transport timeout) any >> further commands "ls /home" succeed. But the log is flooded by >> messages like: >> ----- >> ... skipped ... >> ---- >> This is not so important as the first mentioned issue. But if, for >> example, I turn the node off for a couple of days, then the log will >> grow enormously...
