Bug 1512371
| Summary: | parallel-readdir = TRUE prevents directories listing | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sam McLeod <mailinglists> | |
| Component: | distribute | Assignee: | Poornima G <pgurusid> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.12 | CC: | bugs, mailinglists, nbalacha, pgurusid, ravishankar | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.12.15 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1512437 (view as bug list) | Environment: | ||
| Last Closed: | 2018-10-23 14:21:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | fuse | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1512437, 1529072 | |||
|
Description
Sam McLeod
2017-11-13 03:06:58 UTC
I tried on my local setup, i couldn't reproduce the issue, the directories were listed for me. Will need more details, from which version did you upgrade to 3.12.1?. Which version these directories were created? Does ls not see even the newly created directories? Which version did you start enabling parallel-readdir from? Is it possible to unmount and mount the volume? This is not required as such, instead creating another mount point locally and trying ls, will also do. I was able to hit the issue on a 1 brick distribute volume also, so this is not related to AFR or arbiter as such. When parallel-readdir is enabled, the skip_dirs flag for posix_fill_readdir is set to true. My volinfo: Volume Name: testvol Type: Distribute Volume ID: 0c3b3c49-db17-4c14-95f8-e0e3f8b3f071 Status: Started Snapshot Count: 0 Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 127.0.0.2:/bricks/brick1 Options Reconfigured: diagnostics.count-fop-hits: on diagnostics.latency-measurement: on performance.parallel-readdir: off performance.client-io-threads: true client.event-threads: 10 cluster.favorite-child-policy: size cluster.lookup-optimize: true cluster.readdir-optimize: true cluster.use-compound-fops: true performance.cache-size: 128MB performance.io-thread-count: 32 performance.stat-prefetch: true server.event-threads: 10 performance.write-behind-window-size: 2MB performance.cache-refresh-timeout: 2 transport.address-family: inet nfs.disable: on REVIEW: https://review.gluster.org/18723 (dht: Fill fist_up_subvol before use in dht_opendir) posted (#1) for review on master by Poornima G REVISION POSTED: https://review.gluster.org/18723 (dht: Fill fist_up_subvol before use in dht_opendir) posted (#2) for review on master by Poornima G I just met someone else who was caught unaware by this bug. I was wondering, until it's fixed - is there something you can set on the Gluster server side to prevent clients from ever trying to use the arbiter node? (In reply to Sam McLeod from comment #5) > I just met someone else who was caught unaware by this bug. > > I was wondering, until it's fixed - is there something you can set on the > Gluster server side to prevent clients from ever trying to use the arbiter > node? Sam, this is not related to arbiter (See comment #2). Setting performance.parallel-readdir to off on the volumes should serve as a workaround. This is going to be hit only when parallel-readdir is enabled. And in your use case, there is only 1 distribute, hence there is not much to be made parallel. I would suggest to disable parallel-readdir in this case. Was it that, you saw any perf improvement after enabling parallel-readdir on your setup? The fix for this is part of release 4.1 and 5. As there will be no more 3.12.x releases once version 5 is released, I will close this BZ once 5 is out. REVIEW: https://review.gluster.org/21364 (dht: Fill first_up_subvol before use in dht_opendir) posted (#1) for review on release-3.12 by N Balachandran COMMIT: https://review.gluster.org/21364 committed in release-3.12 by "jiffin tony Thottan" <jthottan> with a commit message- dht: Fill first_up_subvol before use in dht_opendir Reported by: Sam McLeod Change-Id: Ic8f9b46b173796afd70aff1042834b03ac3e80b2 BUG: 1512371 Signed-off-by: Poornima G <pgurusid> 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.12.15, please open a new bug report. glusterfs-3.12.15 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] https://lists.gluster.org/pipermail/announce/2018-October/000114.html [2] https://www.gluster.org/pipermail/gluster-users/ |