Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1630891

Summary: sharding: nfstest creat gets incorrect file size
Product: [Community] GlusterFS Reporter: Kaleb KEITHLEY <kkeithle>
Component: shardingAssignee: Krutika Dhananjay <kdhananj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1CC: bugs, kdhananj, pasik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-06 09:44:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
tcpdump/wireshark .cap/.pcap
none
tcpdump/wireshark .cap/.pcap none

Description Kaleb KEITHLEY 2018-09-19 13:52:31 UTC 
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:
Comment 1 Kaleb KEITHLEY 2018-09-20 12:43:14 UTC 
Created attachment 1485122 [details]
tcpdump/wireshark .cap/.pcap
Comment 2 Kaleb KEITHLEY 2018-09-20 12:43:50 UTC 
Created attachment 1485123 [details]
tcpdump/wireshark .cap/.pcap
Comment 3 Yaniv Kaul 2019-07-01 06:11:27 UTC 
Still relevant? Is anyone looking at this?
Comment 4 Kaleb KEITHLEY 2019-07-01 11:42:23 UTC 
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.
Comment 5 Krutika Dhananjay 2019-07-01 16:06:46 UTC 
(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
Comment 6 Krutika Dhananjay 2020-02-06 09:44:54 UTC 
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.