Bug 1109142 - [SNAPSHOT]: Fails to mount missed snapshot
Summary: [SNAPSHOT]: Fails to mount missed snapshot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1109141
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 10:25 UTC by Avra Sengupta
Modified: 2014-11-11 08:35 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Avra Sengupta 2014-06-13 10:25:51 UTC
+++ This bug was initially created as a clone of Bug #1109141 +++

Description of problem:
If a brick's snapshot is missed, and the brick comes up later, the missed snapshot is not recreated. The mount of the missed snap fails.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-06-13 12:06:39 UTC
REVIEW: http://review.gluster.org/8062 (glusterd/snapshot: Update fstype and fsuuid) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2014-06-14 03:55:35 UTC
COMMIT: http://review.gluster.org/8062 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 7aa3630b1f5e07227e9cd167cbd717bd7932ae78
Author: Avra Sengupta <asengupt>
Date:   Fri Jun 13 11:23:29 2014 +0000

    glusterd/snapshot: Update fstype and fsuuid
    
    Update fstype and fsuuid before creating missed snapshot
    
    Change-Id: Ie9af0065fab288bd1c1a26396428f0cee6335f97
    BUG: 1109142
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/8062
    Reviewed-by: Rajesh Joseph <rjoseph>
    Tested-by: Justin Clift <justin>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 3 Niels de Vos 2014-09-22 12:42:54 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:35:05 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.