Bug 824472

Summary:	writes fail on nfs mount
Product:	[Community] GlusterFS	Reporter:	Rajesh <rajesh>
Component:	rpc	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sachidananda Urs <sac>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	mainline	CC:	amarts, gluster-bugs, saujain, ujjwala, vagarwal, vbellur, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.4.0qa5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-18 13:00:39 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 Rajesh 2012-05-23 14:35:36 UTC

Description of problem:
dbench, bonnie++  or any other writes on an nfs mount fail with the following logs:
[2012-05-23 19:05:59.953881] E [nfs3.c:2279:nfs3svc_write] 0-nfs-nfsv3: Error decoding args
[2012-05-23 19:05:59.958012] E [nfs3.c:2279:nfs3svc_write] 0-nfs-nfsv3: Error decoding args
[2012-05-23 19:05:59.959054] E [nfs3.c:2279:nfs3svc_write] 0-nfs-nfsv3: Error decoding args
.
.
.

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


How reproducible: always


Steps to Reproduce:
1. mount any gluster volume via nfs
2. try to writing on the mount point

Comment 1 Saurabh 2012-05-24 06:53:35 UTC

my setup is sync'ed to this commit id
commit b86436da7e0de47282c46cd14989e4cbaad0501d

and I executed iozone and untar of linux, the nfs.log does not complain about the issue mentioned above.

Are you finding the on the master? as my setup is checked out for release-3.3

Comment 2 Amar Tumballi 2012-05-24 07:18:26 UTC

Saurabh, this happens only on master. Caused by one of my patch, I am looking into this issue.

Comment 3 Sachidananda Urs 2012-05-31 15:24:54 UTC

Amar is there a patch or something you sent that I can cross check?

Comment 4 Amar Tumballi 2012-06-01 06:53:59 UTC

the bug fix is only in upstream, not in release-3.3. Hence moving it out of the ON_QA, and setting MODIFIED (as a standard practice @ Red Hat)

Comment 5 Amar Tumballi 2012-12-18 11:23:24 UTC

Rajesh/Saurabh, I am moving it back to assigned. But can you guys take a resolution? because I see that this bug doesn't have a patch to fix any issues, also comment #1 says its not happening anymore. Please take a appropriate call.

Comment 6 Rajesh 2012-12-18 13:00:39 UTC

works in the latest git head