Description of problem: ======================= Whenever snapshot command is successful against snapname or volumename, the glusterd logs prints a warning message as "invalid snap command" on all the nodes in cluster. For example: ============ [root@rhs-arch-srv2 ~]# gluster snapshot status a40 | grep "Snap Name" Snap Name : a40 [root@rhs-arch-srv2 ~]# glusterd logs: ============== [2014-06-09 09:27:56.478558] W [glusterd-snapshot.c:6489:glusterd_snapshot_postvalidate] 0-management: invalid snap command Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.6.0.14-1.el6rhs.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. Create and start a volume 2. Create a snapshot of a volume 3. Check the status of snapshot using "gluster snapshot status <snap-name> | volume <vol-name>" 4. Check the glusterd logs Actual results: =============== [2014-06-09 09:27:56.478558] W [glusterd-snapshot.c:6489:glusterd_snapshot_postvalidate] 0-management: invalid snap command Expected results: ================= Warning should not be logged for successful and valid snap command.
The patch which fixes this problem has been posted upstream. http://review.gluster.org/#/c/8014/
http://review.gluster.org/#/c/8014/ is merged upstream. However as this bug does not have any blocker flag, I am not going to send the patch downstream until Denali release.
Won't be sending a fix to 3.0. The fix is available in 3.1