Bug 1458215
Summary: | Slave reports ENOTEMPTY when rmdir is executed on master | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> |
Component: | distribute | Assignee: | Nithya Balachandran <nbalacha> |
Status: | CLOSED ERRATA | QA Contact: | Rochelle <rallan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.2 | CC: | akrishna, atumball, bkunal, nbalacha, nchilaka, rallan, rhinduja, rhs-bugs, sheggodu, smali, spalai, srmukher, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.4.z Batch Update 4 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | dht-rm-rf | ||
Fixed In Version: | glusterfs-3.12.2-47 | Doc Type: | Bug Fix |
Doc Text: |
Previously, a race condition in rm -rf operations could leave subdirectories behind on some bricks, causing the operation to fail with the error "Directory not empty". Subsequent rm -rf operations would continue to fail with the same error even though the directories seemed empty when listing their contents from the mount point. These invisible directories needed to be manually deleted on the bricks before the operation would succeed. With this update, the race condition is fixed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-03-27 03:43:36 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: | 1676400, 1677260, 1695403 | ||
Bug Blocks: | 1661258, 1678183 |
Description
Rahul Hinduja
2017-06-02 10:21:56 UTC
After discussing this with Rahul, I am moving this to 3.3.0-beyond. Rahul will try to reproduce this during the regression cycles after enabling debug logs. 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/RHBA-2019:0658 |