Bug 1337394
Summary: | DHT : few Files are not accessible and not listed on mount + more than one Directory have same gfid + (sometimes) attributes has ?? in ls output after renaming Directories from multiple client at same time | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Sakshi <sabansal> |
Component: | distribute | Assignee: | Sakshi <sabansal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.8.0 | CC: | bugs, kramdoss, mzywusko, nbalacha, racpatel, rcyriac, rgowdapp, rhinduja, sabansal, sankarshan, smohan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | dht-gfid-dir,dht-file-access | ||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1336698 | Environment: | |
Last Closed: | 2016-06-16 14:07:31 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: | 1118762, 1118770, 1336698 | ||
Bug Blocks: | 1299184, 1337022 |
Description
Sakshi
2016-05-19 06:11:06 UTC
REVIEW: http://review.gluster.org/14417 (dht: rename takes lock on parent directory if destination exists) posted (#1) for review on release-3.8 by Sakshi Bansal COMMIT: http://review.gluster.org/14417 committed in release-3.8 by Raghavendra G (rgowdapp) ------ commit b82fefed59cd3964c4d667b1645e70825be8e984 Author: Sakshi Bansal <sabansal> Date: Tue May 17 13:23:28 2016 +0530 dht: rename takes lock on parent directory if destination exists For directory rename if destination exists the source directory is created as a child of the given destination directory. Since the new child directory does not exist take lock on parent of the child directory. Backport of http://review.gluster.org/#/c/14371/ > Change-Id: I24a34605a2cd65984910643ff5462f35e8fc7e71 > BUG: 1336698 > Signed-off-by: Sakshi Bansal <sabansal> Change-Id: I24a34605a2cd65984910643ff5462f35e8fc7e71 BUG: 1337394 Signed-off-by: Sakshi Bansal <sabansal> Reviewed-on: http://review.gluster.org/14417 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> 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 |