Red Hat Bugzilla – Bug 826923
xdata ignored in protocol/client for some FOPS
Last modified: 2013-07-24 13:45:00 EDT
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
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.
Commit http://review.gluster.com/3502 fixes the issue.