Bug 826923

Summary:	xdata ignored in protocol/client for some FOPS
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	core	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:45:00 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:

Description Xavi Hernandez 2012-05-31 09:12:31 UTC

Description of problem:

The protocol/client translator does not include, for some FOPS, the xdata argument in the data sent to the remote server.

The involved FOPS are: fsync, lk, opendir, fsetattr and writev


Version-Release number of selected component (if applicable): 3.3.0


How reproducible: Any non-empty xdata sent using one of these FOPS from the client is received as a NULL xdata in the server side.


Actual results: xdata is NULL on the server side


Expected results: xdata should contain the same values on the server side it had on the client side

Comment 1 Amar Tumballi 2012-05-31 10:08:03 UTC

Xavier, thanks for finding it out. On master, 'writev' issue is already fixed. If you are planing to use xdata, i recommend master branch on git. We will fix the other fops soon.

Comment 2 Raghavendra Bhat 2012-06-11 11:31:14 UTC

Commit http://review.gluster.com/3502 fixes the issue.