Description of problem: gluster 2x2 distribute+replica with features.shard = enable. NFS-Ganesha 2.7.0, libntirpc-1.7.0, glusterfs-4.1.4 nfstest creat tests creates a file, writes 8x8K chunks. At the commit, the attr returned shows the file size as < 65536. with features.shard = disable the test passes, attr returned shows the file size as 65536. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1485122 [details] tcpdump/wireshark .cap/.pcap
Created attachment 1485123 [details] tcpdump/wireshark .cap/.pcap
Still relevant? Is anyone looking at this?
I expect it is still relevant. I wonder how it escaped triage and assignment. Based on the date I believe it was found and filed during last fall's Bake-a-thon.
(In reply to Kaleb KEITHLEY from comment #4) > I expect it is still relevant. I wonder how it escaped triage and assignment. > > Based on the date I believe it was found and filed during last fall's > Bake-a-thon. 1. Please share the exact command(s) used to do the writes. 2. And also the xattrs of the main file from the backend. 3. Also include the volume info output. -Krutika
Sharding is currently only supported for the limited use-cases of vm image storage and gluster-block backend. The test case described above falls in the unsupported category. Hence closing the bz.