[Bugs] [Bug 1147236] gluster 3.6.0 compatibility issue with gluster 3.3

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1147236



--- Comment #1 from Panpan Feng <jiaowopan at gmail.com> ---
Hi all , I have done more tests in my environment. After  I debug the glusterfs
3.6.0 beta2, I have more information of the compatibility issue.

I find when I preform a write operation , the variable req.rpc_status is -1 in
xlators/protocol/client/src/client-rpc-fops.c:810  function
(client3_3_writev_cbk).

To find out who set rpc_status to -1, I add some debug log in all corresponding
files. Then I re-run the process, and write a file. 

In the log file, I find that in rpc/rpc-lib/src/rpc-clnt.c:579 function
(rpc_clnt_reply_fill), the rpc_status has been set to -1 .

if ((rpc_reply_status (replymsg) == MSG_DENIED)
      || (rpc_accepted_reply_status (replymsg) != SUCCESS)){
    req->rpc_status = -1;
}

Then I log out rpc_reply_status (replymsg)  and  rpc_accepted_reply_status
(replymsg) , which is 0  and  4 seperately. Then I search google, 0 means
MSG_ACCEPTED, and 4 means GARBAGE_ARGS. 
So the rpc connection is accepted, but there is garbage arguments in the rpc
message body. 

So anybody can tell me what should I do next?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4PPy64jmGO&a=cc_unsubscribe