Bug 1105484
| Summary: | [SNAPSHOT] : A brick volume-id is changed after reboot of the brick's node | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | rjoseph |
| Component: | core | Assignee: | rjoseph |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | bugs, gluster-bugs, nsathyan, spandura, ssamanta |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | SNAPSHOT | ||
| Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1100211 | Environment: | |
| Last Closed: | 2014-11-11 08:34:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1100211 | ||
| Bug Blocks: | |||
|
Comment 1
Anand Avati
2014-06-06 09:11:50 UTC
REVIEW: http://review.gluster.org/8002 (glusterd/snapshot: Update file-system uuid during snap creation) posted (#2) for review on master by Rajesh Joseph (rjoseph) REVIEW: http://review.gluster.org/8002 (glusterd/snapshot: Update file-system uuid during snap creation) posted (#3) for review on master by Rajesh Joseph (rjoseph) COMMIT: http://review.gluster.org/8002 committed in master by Krishnan Parthasarathi (kparthas) ------ commit f1705e2d338704806cbd90ec9d0d66c0b16cc2ef Author: Rajesh Joseph <rjoseph> Date: Thu Jun 5 10:00:33 2014 +0530 glusterd/snapshot: Update file-system uuid during snap creation After the brick snapshot file-system UUID of the origin brick and the snapshot brick will be identical. If user is using file-system UUID to mount the backend bricks then this will result in unexpected behaviour. Fix: After taking the LVM snapshot create new UUID for the snapshot brick. Change-Id: I339c90abd72dd392de195b674ea22217e63dfd48 BUG: 1105484 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/8002 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas> REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: Add read-only option to XFS mount) posted (#1) for review on master by Harshavardhana (harsha) REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: Add read-only option to XFS snapshot mounts) posted (#2) for review on master by Harshavardhana (harsha) REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: - Fail mount() on cross platforms as its not portable) posted (#3) for review on master by Harshavardhana (harsha) REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: - linux mount() is not portable, fail on OSX) posted (#4) for review on master by Harshavardhana (harsha) REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: - linux mount() is not portable, fail on OSX) posted (#5) for review on master by Harshavardhana (harsha) REVIEW: http://review.gluster.org/8066 (glusterd/snapshot: - linux mount() is not portable, fail on OSX) posted (#6) for review on master by Harshavardhana (harsha) 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/ 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 |