Description of problem: Snapshot is supported only for thinly provisioned LV. Therefore to take snapshot all the bricks of the volume must be on thinly provisioned LV, Snapshot command does fail if one or more brick(s) are thick LV, but the error message is not clear. It fails with the following error message: "snapshot create: failed: Commit failed on localhost. Please check log file for details." Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Snapshot command fail if one or more brick(s) are thick LV, but the error message is not clear. It fails with the following error message: "snapshot create: failed: Commit failed on localhost. Please check log file for details." Expected results: Snapshot command should fail with accurate error message. Additional info:
REVIEW: http://review.gluster.org/8377 (glusterd/snapshot: Proper err msg for snapshot create command) posted (#1) for review on master by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/8377 (glusterd/snapshot: Proper err msg for snapshot create command) posted (#2) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/8377 (glusterd/snapshot: Proper err msg for snapshot create command) posted (#3) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/8377 (glusterd/snapshot: Proper err msg for snapshot create command) posted (#4) for review on master by Krishnan Parthasarathi (kparthas)
COMMIT: http://review.gluster.org/8377 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 8732ee5319bfe4649473c29458a6ab65b73d5516 Author: Rajesh Joseph <rjoseph> Date: Sun Jul 27 10:36:52 2014 -0400 glusterd/snapshot: Proper err msg for snapshot create command problem: Snapshot command fails if one or more bricks are not thinly provisioned. But the error message is a generic error message which is confusing to the user. fix: Provide correct error message in case of failure. Change-Id: Iad247f966423a8f73ef6da57cab7ed6cddc05861 BUG: 1123646 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/8377 Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user