Red Hat Bugzilla – Bug 1559884
Linkto files visible in mount point
Last modified: 2018-10-01 04:37:51 EDT
Description of problem: On a distribute volume, if the below set of options are enabled: cluster.rebal-throttle: aggressive performance.rda-cache-limit: 300Mb server.allow-insecure: on performance.readdir-ahead: on performance.force-readdirp: on storage.batch-fsync-delay-usec: 0 cluster.min-free-disk: 120GB nfs.disable: on performance.stat-prefetch: off cluster.weighted-rebalance: on transport.address-family: inet cluster.lookup-optimize: off performance.parallel-readdir: on auto-delete: disable The linkto files will be visible on the mount point https://bugzilla.redhat.com/show_bug.cgi?id=1523258#c69 I created a pure distribute volume with 3 bricks, created and renamed files so there would be linkto files created: [root@rhgs313-6 ~]# mount -t glusterfs -s 192.168.122.6:/rebal1 /mnt/fuse1 [root@rhgs313-6 ~]# cd /mnt/fuse1 [root@rhgs313-6 fuse1]# l /bricks/brick1/rebal1-* /bricks/brick1/rebal1-1: total 4.0K -rw-r--r--. 2 root root 5 Mar 22 23:20 FILE-2 /bricks/brick1/rebal1-2: total 4.0K -rw-r--r--. 2 root root 5 Mar 22 23:20 AJKAJDNAL ---------T. 2 root root 0 Mar 22 23:20 FILE-2 /bricks/brick1/rebal1-3: total 0 ---------T. 2 root root 0 Mar 22 23:21 AJKAJDNAL [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# l /bricks/brick1/rebal1-* /bricks/brick1/rebal1-1: total 4.0K -rw-r--r--. 2 root root 5 Mar 22 23:20 FILE-2 /bricks/brick1/rebal1-2: total 4.0K -rw-r--r--. 2 root root 5 Mar 22 23:20 AJKAJDNAL ---------T. 2 root root 0 Mar 22 23:20 FILE-2 /bricks/brick1/rebal1-3: total 0 ---------T. 2 root root 0 Mar 22 23:21 AJKAJDNAL [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# With the default options, linkto files are not visible on the mount point: [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# l total 1.0K -rw-r--r--. 1 root root 5 Mar 22 23:20 AJKAJDNAL -rw-r--r--. 1 root root 5 Mar 22 23:20 FILE-2 [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# Set the options enabled on mediaset: [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.readdir-ahead on volume set: success [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.rda-cache-limit 300Mb volume set: success [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.force-readdirp on volume set: success [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.stat-prefetch off volume set: success [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.parallel-readdir on volume set: success [root@rhgs313-6 fuse1]# [root@rhgs313-6 fuse1]# l total 1.0K -rw-r--r--. 1 root root 5 Mar 22 23:20 AJKAJDNAL ---------T. 1 root root 0 Mar 22 23:21 AJKAJDNAL -rw-r--r--. 1 root root 5 Mar 22 23:20 FILE-2 ---------T. 1 root root 0 Mar 22 23:20 FILE-2 [root@rhgs313-6 fuse1]# gluster v set rebal1 performance.parallel-readdir off volume set: success [root@rhgs313-6 fuse1]# l total 1.0K -rw-r--r--. 1 root root 5 Mar 22 23:20 AJKAJDNAL -rw-r--r--. 1 root root 5 Mar 22 23:20 FILE-2 [root@rhgs313-6 fuse1]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Patch merged upstream : https://review.gluster.org/#/c/19172/
Created attachment 1437202 [details] rhgs34_logs
Reproduced this on a RHGS 3.3.1 setup: - where the said options were enabled on a plain distribute volume -> files' create-rename done to have T-files present from a fuse mount -> (Mountpoint displayed T-files) -> parallel-readdir disabled -> (Mountpoint did not display T-files) -> parallel-readdir enabled and stat-prefetch enabled -> (Mountpoint did not display T-files) Tried the exact same steps on the build glusterfs-3.12.2-10.el7rhgs.x86_64. - where mountpoint never displayed T-files in any of the steps.. irrespective of parallel-readdir enabled/disabled, or stat-prefetch enabled/disabled. In other words, no dependency seen between paralled-readdir and stat-prefetch to be enabled together. Moving this bug to verified. PFA detailed 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/RHSA-2018:2607