Bug 1505323
Summary: | When sub-dir is mounted on Fuse client,adding bricks to the same volume unmounts the subdir from fuse client | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Amar Tumballi <atumball> |
Component: | protocol | Assignee: | Amar Tumballi <atumball> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.12 | CC: | bugs, msaini, rhs-bugs, storage-qa-internal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.13.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1503413 | Environment: | |
Last Closed: | 2017-11-22 10:45:42 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: | 1503413 | ||
Bug Blocks: |
Comment 1
Amar Tumballi
2017-10-23 10:39:38 UTC
REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#3) for review on master by Amar Tumballi (amarts) REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#4) for review on master by Amar Tumballi (amarts) REVIEW: https://review.gluster.org/18550 (protocol/client: handle the subdir handshake properly for add-brick) posted (#5) for review on master by Amar Tumballi (amarts) COMMIT: https://review.gluster.org/18550 committed in master by Amar Tumballi (amarts) ------ commit 9aa574a51b84717c1f3949ed2e28a49e49840a93 Author: Amar Tumballi <amarts> Date: Sun Oct 22 12:41:38 2017 +0530 protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> COMMIT: https://review.gluster.org/18550 committed in master by \n\n -------------\n\n protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> COMMIT: https://review.gluster.org/18550 committed in master by ------------- protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> COMMIT: https://review.gluster.org/18550 committed in master by ------------- protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> REVIEW: https://review.gluster.org/18586 (protocol/client: handle the subdir handshake properly for add-brick) posted (#1) for review on release-3.12 by Amar Tumballi COMMIT: https://review.gluster.org/18586 committed in release-3.12 by ------------- protocol/client: handle the subdir handshake properly for add-brick There should be different way we handle handshake in case of subdir mount for the first time, and in case of subsequent graph changes. Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54 BUG: 1505323 Signed-off-by: Amar Tumballi <amarts> (cherry picked from commit 9aa574a51b84717c1f3949ed2e28a49e49840a93) glusterfs-3.12.3 has the fix 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-glusterfs-3.12.3, please open a new bug report. glusterfs-glusterfs-3.12.3 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://lists.gluster.org/pipermail/gluster-devel/2017-November/053983.html [2] https://www.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.13.0, please open a new bug report. glusterfs-3.13.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://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/ |