Bug 1118770
Summary: | DHT : If Directory creation is in progress and rename of that Directory comes from another mount point then after both operation few files are not accessible and not listed on mount and more than one Directory have same gfid | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rachana Patel <racpatel> | |
Component: | distribute | Assignee: | Raghavendra G <rgowdapp> | |
Status: | CLOSED ERRATA | QA Contact: | Prasad Desala <tdesala> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.0 | CC: | amukherj, avasudev, bmohanra, nbalacha, nchilaka, rcyriac, rgowdapp, rhinduja, sankarshan, sheggodu, smohan, spalai, srmukher | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.4.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | triaged,hotfix, dht-directory-consistency, dht-3.2.0-proposed, rebase | |||
Fixed In Version: | glusterfs-3.12.2-1 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, rename and lookup option were not synchronized. The source gfid was not always associated with destination path once rename is complete and hence contents of the directories were not visible. This resulted in the creation of different directories with the same gfid.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1252244 1328473 (view as bug list) | Environment: | ||
Last Closed: | 2018-09-04 06:26:56 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: | 1369312 | |||
Bug Blocks: | 1118762, 1252244, 1311843, 1324381, 1336698, 1337022, 1337394, 1345828, 1503134 |
Description
Rachana Patel
2014-07-11 13:43:26 UTC
In case if destination directory exist, output would be rename1 already exist and race :- [root@OVM1 race]# mkdir rename [root@OVM1 race1]# mv rename rename1 output on mount:- [root@OVM5 race]# ls -lR .: total 0 drwxr-xr-x 2 root root 18 Jul 10 15:00 rename drwxr-xr-x 3 root root 57 Jul 10 15:00 rename1 ./rename: total 0 ./rename1: total 0 drwxr-xr-x 2 root root 18 Jul 10 15:00 rename ./rename1/rename: total 0 bricks:- [root@OVM5 race]# tree /brick*/race/ /brick1/race/ ├── rename └── rename1 └── rename /brick2/race/ ├── rename └── rename1 └── rename /brick3/race/ ├── rename └── rename1 └── rename 9 directories, 0 files [root@OVM5 race]# getfattr -d -m . -e hex /brick3/race/* -R getfattr: Removing leading '/' from absolute path names # file: brick3/race/rename trusted.gfid=0xac6b95cb620c400d91a55f3ce66ee005 trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff # file: brick3/race/rename1 trusted.gfid=0x9482dd3bf0834596bb74d6ffeffa40d2 trusted.glusterfs.dht=0x00000001000000000000000055555554 # file: brick3/race/rename1/rename trusted.gfid=0xac6b95cb620c400d91a55f3ce66ee005 trusted.glusterfs.dht=0x0000000100000000aaaaaaaaffffffff Triage Update: RCA is known. Design and fix need to be done. Sakshi, Is there a reason, you moved the bug back to MODIFIED? The patch is already merged. Can you please revisit and move the bug to modified if there is no valid reason? regards, Raghavendra The issue reported in the bug is still seen in build - glusterfs-3.7.9-4.el7rhgs.x86_64 With parallel mkdir and rename operation, mismatching gfids is seen on the directory under test. Moving this back to assigned. Thanks raghavendra, I have updated the doc text further, let me know if this looks ok. Doc text seems fine too. upstream patch https://review.gluster.org/15472 fixes this issue Verified this BZ on glusterfs version 3.12.2-7.el7rhgs.x86_64. Ran testcases mentioned in description, Comment2 and Comment16. I didn't see any gfid mismatch on the directory under test. Moving this BZ to Verified. Updated the doc text. Kindly review and confirm Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607 |