Bug 1232378
| Summary: | [remove-brick]: Creation of file from NFS writes to the decommissioned subvolume and subsequent lookup from fuse creates a link | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Susant Kumar Palai <spalai> | |
| Component: | distribute | Assignee: | Susant Kumar Palai <spalai> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | amukherj, bugs, gluster-bugs, nbalacha, nsathyan, rgowdapp, rhinduja, rhs-bugs, spalai, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | Reopened, Triaged | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1225452 | |||
| : | 1256283 (view as bug list) | Environment: | ||
| Last Closed: | 2016-06-16 13:12:44 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: | 1225452 | |||
| Bug Blocks: | 1223636, 1227687, 1256283 | |||
|
Comment 1
Anand Avati
2015-06-16 15:18:21 UTC
REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#3) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#4) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#5) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#6) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#7) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#8) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#9) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#10) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#11) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#12) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#13) for review on master by Susant Palai (spalai) REVIEW: http://review.gluster.org/11260 (dht: block/handle create op falling to decommissioned brick) posted (#14) for review on master by Susant Palai (spalai) COMMIT: http://review.gluster.org/11260 committed in master by Raghavendra G (rgowdapp) ------ commit 1626fb105c99ef623be3687f3f48d9247ab9b7c4 Author: Susant Palai <spalai> Date: Tue Jun 16 20:35:46 2015 +0530 dht: block/handle create op falling to decommissioned brick Problem: Post remove-brick start till commit phase, the client layout may not be in sync with disk layout because of lack of lookup. Hence,a create call may fall on the decommissioned brick. Solution: Will acquire a lock on hashed subvol. So that a fix-layout or selfheal can not step on layout while reading the layout. Even if we read a layout before remove-brick fix-layout and the file falls on the decommissioned brick, the file should be migrated to a new brick as per the fix-layout. Change-Id: If84a12ec34f981adb2b9b224e80f535cfe5bf9f2 BUG: 1232378 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/11260 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user *** Bug 1227687 has been marked as a duplicate of this bug. *** |