Bug 763661 (GLUSTER-1929)

Summary: different value is logged for read header size for multiple reads
Product: [Community] GlusterFS Reporter: Raghavendra G <raghavendra>
Component: transportAssignee: Raghavendra G <raghavendra>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTP Mount Type: fuse
Documentation: DNR CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vijay Bellur 2010-10-12 07:04:08 UTC
PATCH: http://patches.gluster.com/patch/5478 in master (rpc-transport/socket: initialize fragcurrent pointer in correct state while reading vectored replies.)

Comment 1 Raghavendra G 2010-10-12 09:19:42 UTC
Configuration: single process distributed replicate.

Test: dbench/kernel compile.

Issue: When lengths of two vectors returned from socket to rpc are logged, length of the first vector (which is sum of rpc-header and read proc header lengths) are found to be too high (in terms of 10s of KBs) and different for different read calls. read proc header size is less than 256 bytes and it should be constant for multiple read calls.