This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Patch(es) available on kernel-2.6.32-90.el6

*** Bug 634438 has been marked as a duplicate of this bug. ***

Created attachment 489325 [details]
pynfs log on i386

(In reply to comment #6)
> *** Bug 634438 has been marked as a duplicate of this bug. ***

hi J.Bruce,
I run pynfs on RHEL6.1 and verified bz634438 problem fixed, but there are two new problems occurs on, could you help to look at it?
first question, pynfs initialization failed on x86_64 arch and i386 has no problem of it.
# ./testserver.py --outfile TESTOUT.log --maketree localhost:/nfs all
noutf8 | tee -a pynfs_log
Starting Call Back server stub on port 48313
Starting Call Back server stub on port 48513
Initialization failed, no tests run.
Creating file /nfs/tree/file: operation OP_OPEN should return NFS4_OK,
instead got NFS4ERR_GRACE

[root@hp-xw6400-02 pynfs]# uname -a
Linux hp-xw6400-02.lab.bos.redhat.com 2.6.32-122.el6.x86_64 #1 SMP Wed
Mar 9 23:54:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@hp-xw6400-02 pynfs]# rpm -qa|grep nfs-utils
nfs-utils-1.2.3-4.el6.x86_64
nfs-utils-lib-1.1.5-3.el6.x86_64

So do you know how should I do? Btw, I run according to http://fedoraproject.org/wiki/QA:Testcase_nfs_pynfs


second question, I compared the test result on i386 with known failures and
there are extra failure occurs on, could you help to check below failure? Attached is the full log if you need.
RD9      st_read.testBadStateid                                   :
FAILURE
           READ with bad stateid should return
           NFS4ERR_BAD_STATEID, instead got NFS4ERR_EXPIRED

WRT10    st_write.testBadStateid                                  :
FAILURE
           WRITE with bad stateid should return
           NFS4ERR_BAD_STATEID, instead got NFS4ERR_EXPIRED

Thanks in advance.

"Creating file /nfs/tree/file: operation OP_OPEN should return NFS4_OK,
instead got NFS4ERR_GRACE"

Just add a delay after starting the nfs server that is longer than the grace period, before running the tests.

(One way to do this is just to mount the server and open a file, e.g. with "cat /mnt/somefile"; the open won't normally succeed till the grace period ends.)

I believe the RD9 and WRT10 failures can safely be ignored.

(In reply to comment #9)
> "Creating file /nfs/tree/file: operation OP_OPEN should return NFS4_OK,
> instead got NFS4ERR_GRACE"
> 
> Just add a delay after starting the nfs server that is longer than the grace
> period, before running the tests.
> 
> (One way to do this is just to mount the server and open a file, e.g. with "cat
> /mnt/somefile"; the open won't normally succeed till the grace period ends.)
> 
> I believe the RD9 and WRT10 failures can safely be ignored.

thank you, pynfs test passed on x86_64 and no extra issue found.

Created attachment 490466 [details]
pynfs log on x86_64

code review and verified that these patch applied is sane.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0542.html