Created attachment 1050103 [details]
packet_trace_of_read

Created attachment 1050105 [details]
packet_trace_of_write

I have verified the bug using following steps :

1.) Created a storage trusted pool of 4 nodes ,each running with redhat gluster storage
2.) Create 6x2 volume out of it
Volume Name: testvol
Type: Distributed-Replicate
Volume ID: 2dd3e92b-b40e-4fde-8a45-d0fe64ae458f
Status: Started
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Bricks:
Brick1: 10.70.43.73:/brick/b11
Brick2: 10.70.43.63:/brick/b12
Brick3: 10.70.43.73:/brick/b21
Brick4: 10.70.43.36:/brick/b22
Brick5: 10.70.43.36:/brick/b31
Brick6: 10.70.43.63:/brick/b32
Brick7: 10.70.43.73:/brick/b41
Brick8: 10.70.43.63:/brick/b42
Brick9: 10.70.43.73:/brick/b51
Brick10: 10.70.43.36:/brick/b52
Brick11: 10.70.43.36:/brick/b61
Brick12: 10.70.43.63:/brick/b62
Options Reconfigured:
features.cache-invalidation: on
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
nfs.disable: on
performance.readdir-ahead: on


3.) export the volume using nfs-ganesha
4.) mount the volume using nfsv4.1 protocol
5.) write and read 50 files (perform I/Os)
6.) take the packet trace and verified it does not contain pnfs ops like LAYOUTGET, GETDEVICEINFO etc

I tested it both in rhel6.7 and rhel7.1 clients

I am also attaching the packet trace with bug

based on comment#4, moving this BZ to verified.

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://rhn.redhat.com/errata/RHSA-2015-1495.html