I thought I fixed this the last time around. Clearly, I didn't! I found the root cause. I will be sending out a patch soon. The problem is that rpc_clnt_disconnect doesn't disable the reconnect logic. The rpc object treats an active disconnect and a 'broken' transport alike. I am not sure why volume-status isn't working. It could be a different issue. Could you provide the set of commands that were issued before you started observing volume-status command isn't working? Alternately, you could attach the glusterd log and the service's logs, whose status is incorrectly reported if you have them handy. ~kp reported. ----- Original Message ----- > Atin Mukherjee <amukherj@xxxxxxxxxx> wrote: > > > I will take a look at it. In past we have seen readv failure logs in > > glusterd, need to check whether the root cause is same or not. Will keep > > you posted. > > Well, there are two problems: first it fills the logs, and second, > gluster volume status does not work. > > -- > Emmanuel Dreyfus > http://hcpnet.free.fr/pubz > manu@xxxxxxxxxx > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
