Bug 1114542

Summary: nfs-ganesha: posix compliance test gets stuck
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Saurabh <saujain>
Component: nfs-ganeshaAssignee: Soumya Koduri <skoduri>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: mzywusko, nlevinki, nsathyan, skoduri
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-27 07:13:14 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:
Attachments:
Description Flags
nfs-ganesha.log none

Description Saurabh 2014-06-30 10:09:56 UTC 
Description of problem:
Enabled nfs-ganesha as per the recommended steps for a 6x2 volume on 4 node RHS cluster
Started posix compliace test on nfs mount, mounted the volume with vers=3 as the option. 


Version-Release number of selected component (if applicable):
glusterfs-3.6.0.22-1.el6rhs.x86_64


How reproducible:
always

Actual results:

from RHS node1,
[root@nfs1 ~]# strace -p 8874
Process 8874 attached - interrupt to quit
futex(0x7fcbb61fc9d0, FUTEX_WAIT, 8898, NULL

from client node,

posix test related process information,
[root@rhsauto034 ~]# ps -auxww| grep  6035
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
root      6035  0.0  0.2 142796 10352 pts/0    S+   03:02   0:00 /usr/bin/perl /usr/bin/prove -r /opt/qa/tools/pjd-fstest-20080816/tests/
root      9334  0.0  0.0 103244   836 pts/1    S+   03:38   0:00 grep 6035

[root@rhsauto034 ~]# strace -p 6035
Process 6035 attached - interrupt to quit
select(8, [4 6], NULL, NULL, NULL


actual posix compliance test result,
[root@rhsauto034 posix]# time prove -r /opt/qa/tools/pjd-fstest-20080816/tests/
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/00.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/01.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/02.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/03.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/04.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/05.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/06.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/07.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/08.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/09.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/10.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/11.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/12.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chflags/13.t ... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/00.t ..... Failed 1/58 subtests 
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/01.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/02.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/03.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/04.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/05.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/06.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/07.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/08.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/09.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/10.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chmod/11.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chown/00.t ..... ok       
/opt/qa/tools/pjd-fstest-20080816/tests/chown/01.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/02.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/03.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chown/04.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/05.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chown/06.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/07.t ..... ok     
/opt/qa/tools/pjd-fstest-20080816/tests/chown/08.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/09.t ..... ok   
/opt/qa/tools/pjd-fstest-20080816/tests/chown/10.t ..... ok    
/opt/qa/tools/pjd-fstest-20080816/tests/link/00.t ...... 70/80 ---- stuck at this point

Expected results:
posix compliance should not get stuck.

Additional info:
Comment 1 Saurabh 2014-06-30 10:11:57 UTC 
Created attachment 913295 [details]
nfs-ganesha.log
Comment 3 Soumya Koduri 2014-07-07 11:40:05 UTC 
This issue could not be reproduced. It doesnt get stuck for version=3.

Please change the defect summary to reflect the problem/close the bug and reopen if any failures are seen.

In any case, POSIX complaince test failures are not blockers for tech-preview refresh in Denali. Will be addressed in the next release.
Comment 4 Soumya Koduri 2015-07-06 09:21:05 UTC 
We are able to run the posix-compliance tests. Please re-run the tests and confirm if you still see the issue.
Comment 6 Soumya Koduri 2016-01-27 07:13:14 UTC 
This issue is not seen anymore. posix-complaince tests on nfs-ganesha volume were being run successfully lately. Closing it for now.

Please re-open if the issue is seen again.