Bug 763661 (GLUSTER-1929) - different value is logged for read header size for multiple reads
Summary: different value is logged for read header size for multiple reads
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1929
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 09:19 UTC by Raghavendra G
Modified: 2015-12-01 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: fuse
Documentation: DNR
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.