Bug 1287538 - [Snapshot]: Clone creation fails on tiered volume with pre-validation failed message
Summary: [Snapshot]: Clone creation fails on tiered volume with pre-validation failed ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.7.6
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On: 1278254 1279327
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 10:10 UTC by Avra Sengupta
Modified: 2016-04-19 07:49 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.7.7
Clone Of: 1279327
Environment:
Last Closed: 2016-02-15 08:55:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-12-02 10:17:05 UTC
REVIEW: http://review.gluster.org/12846 (snapshot/clone : Fix tier pause failure for snapshot clone) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2015-12-03 05:58:59 UTC
COMMIT: http://review.gluster.org/12846 committed in release-3.7 by Rajesh Joseph (rjoseph) 
------
commit d84242276b2f8ee7151c7784992dffb651816ccf
Author: Avra Sengupta <asengupt>
Date:   Mon Nov 9 13:37:53 2015 +0530

    snapshot/clone : Fix tier pause failure for snapshot clone
    
        Backport of http://review.gluster.org/#/c/12548
    
    On a tiered volume, snapshot clone fails while trying to
    pause tier, as we pass volname(snap) to the brick_op_phase module,
    which tries to look for the snap volume amongst regular
    volumes, and obviously doesn't find it and fail.
    
    Well as snapshot volumes are read only volume, and will not
    have tiering daemon acting upon them, there is really no need
    to pause tiereing while taking clone of snapshot volumes. Hence
    removing the code to pause and resume tiering during clone create.
    
    Change-Id: I2266aba589a830a13a806c0d8a56fd8855143ccd
    BUG: 1287538
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/12846
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Kaushal 2016-04-19 07:49:44 UTC
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.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.