I wrote a simple nagios plugin in C that calls gluster volume status to check taht all bricks are online (is it of any interest to someone else than me? What name would you expect for it? Does check_gfbricks looks sane?) The thing periodically reported offline bricks and I did not understood why, until I realized that the peers all run the test at the same time, and hence may fail to lock the volume because another peer already holds the lock. It seems that a failed lock acquisition is reported as offline bricks for the peer. The simple workaround is to not check at the same time, but perhaps the reported data could be improved? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
