+++ This bug was initially created as a clone of Bug #1463592 +++

Description of problem:
On enabling parallel-readdir, mount the volume and run IOs we get to see warning messages saying 'parallel-readdir' is not recognized.

This has no impact on fuctionality.

Version-Release number of selected component (if applicable):
samba-4.6.3-3.el7rhgs.x86_64
glusterfs-3.8.4-28.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Enable parallel-readdir on volume
2.mount on windows client
3.Run IOs as in simple file creation
4.Check client logs

Actual results:
Warning messages as 'parallel-readdir' is not recognized

Expected results:
Should not get any warning messages

Additional info:
[2017-06-20 10:14:06.243354] W [MSGID: 101174] [graph.c:360:_log_if_unknown_option] 0-topgun-readdir    -ahead-1: option 'parallel-readdir' is not recognized
 73 [2017-06-20 10:14:06.243388] W [MSGID: 101174] [graph.c:360:_log_if_unknown_option] 0-topgun-readdir    -ahead-0: option 'parallel-readdir' is not recognized
 74 [2017-06-20 10:14:06.243592] I [MSGID: 104045] [glfs-master.c:91:notify] 0-gfapi: New graph 64686370    -3437-2d31-3237-2e6c61622e65 (0) coming up


Volume Name: topgun
Type: Distributed-Replicate
Volume ID: 7a2b0cc2-134e-4c28-b901-7a66fa80d660
Status: Started
Snapshot Count: 8
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dhcp47-127.lab.eng.blr.redhat.com:/bricks/brick5/topgun_brick0
Brick2: dhcp46-181.lab.eng.blr.redhat.com:/bricks/brick5/topgun_brick1
Brick3: dhcp46-47.lab.eng.blr.redhat.com:/bricks/brick4/topgun_brick2
Brick4: dhcp47-140.lab.eng.blr.redhat.com:/bricks/brick4/topgun_brick3
Options Reconfigured:
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
performance.cache-samba-metadata: on
network.inode-lru-limit: 50000
performance.md-cache-timeout: 600
performance.cache-invalidation: on
features.cache-invalidation-timeout: 600
features.cache-invalidation: on
nfs.disable: off
transport.address-family: inet
server.allow-insecure: on
performance.stat-prefetch: on
storage.batch-fsync-delay-usec: 0
performance.parallel-readdir: on
features.uss: enable
features.show-snapshot-directory: enable
features.barrier: disable
performance.nl-cache: on
performance.nl-cache-timeout: 600
cluster.brick-multiplex: disable

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-06-21 05:29:08 EDT ---

This bug is automatically being proposed for the current release of Red Hat Gluster Storage 3 under active development, by setting the release flag 'rhgs‑3.3.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

--- Additional comment from Poornima G on 2017-06-21 06:01:00 EDT ---

There is no functional impact with this log message, its because there is an entry for "parallel-readdir" in glusterd-volume-set.c but not in readdir-ahead.c, hence the options not defined error. This log message is seen only during graph init i.e. start of the client or any volume sets.

Thus i would suggest that we defer it for 3.3

--- Additional comment from Atin Mukherjee on 2017-06-21 07:17:09 EDT ---

Vivek,

Can we have an agreement to defer this from 3.3.0, from any angle this doesn't look like a blocker.

--- Additional comment from Vivek Das on 2017-06-22 03:17:09 EDT ---

(In reply to Atin Mukherjee from comment #3)
> Vivek,
> 
> Can we have an agreement to defer this from 3.3.0, from any angle this
> doesn't look like a blocker.

As there is no functional impact, yes we can well defer from 3.3.0.

--- Additional comment from Atin Mukherjee on 2017-06-22 03:25:55 EDT ---

Based on comment 4, deferring this bug from 3.3.0.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-06-28 05:06:31 EDT ---

This BZ having been considered, and subsequently not approved to be fixed at the RHGS 3.3.0 release, is being proposed for the next minor release of RHGS