Bug 1113975 - [SNAPSHOT] : Restoring the snap-volume once the volume is already restored results in a failure.
Summary: [SNAPSHOT] : Restoring the snap-volume once the volume is already restored re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1113961
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-27 11:23 UTC by Avra Sengupta
Modified: 2014-11-11 08:36 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of: 1113961
Environment:
Last Closed: 2014-11-11 08:36:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-06-27 11:41:54 UTC
REVIEW: http://review.gluster.org/8192 (glusterd/snapshot: Correct the mount path check) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2014-06-30 09:27:10 UTC
COMMIT: http://review.gluster.org/8192 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit a39d94589eb626c28ae9b06bcc898ebf00147a59
Author: Avra Sengupta <asengupt>
Date:   Fri Jun 27 11:38:57 2014 +0000

    glusterd/snapshot: Correct the mount path check
    
    Before removing a lvm, we check if the lvm is mounted
    on the brick path. If not, we remove the brick path only.
    Correcting this check to support restore cases, where the
    volname is not the non-hyphanated uuid, but the original
    volume's name.
    
    Change-Id: If158f4651d36efa2f94523458faf826230e9c76a
    BUG: 1113975
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/8192
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>
    Tested-by: Justin Clift <justin>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Sachin Pandit <spandit>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 3 Niels de Vos 2014-09-22 12:44:00 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:36:12 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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