Description of problem:
Having a configuration in which the server is RHEL5.1 Gold and the client is
AIX 6.1.0 SP2, when I run the test5 basic command (-b) of the connectathon suite
on AIX after doing a NFSV4 mount I get the following errors:
./runtests -b -t /mnt/nosec/test5
Starting BASIC tests: test directory /mnt/nosec/test5 (arg: -t)
./test5: read and write
./test5: (/mnt/nosec/test5) 'bigfile' has size 1048576, should be 0
basic tests failed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We have the error because the asked TRUNCATION is ineffective. If we suppress
the TRUNCTATION in the test5, it works.
On the AIX side, open and truncate the file are done all at once. but
linux looks to split it into two operations, it opens first and then truncate.
Another analyse on the AIX side gives the following:
>At this point the file size is 1048576.
>>The client send the following compound request over to the server.
>>OP_OPEN, with size of 0.
>>OP_NVERIFY, with the file verifier when the file size is 1048576.
>>The server reply with
>>OP_PUTFH --- NFS4_OK
>>OP_OPEN --- NFS4_OK
>>OP_NVERIFY --- NFS4ERR_SAME
>>One would think that if server return NFS4_OK for OP_OPEN that OP_OPEN
>operation was successful and that the file size has been truncated to 0. And
>since file size has been truncated from 1048576 to 0. So the file verifier
>should be different than the one that client sent (the one when the file size
>is 1048576). Which means the OP_NVERIFY should return NFS4_OK because it's not
>the same. But in this case, linux actually return the same. I think this is a
>>Keep in mind that I do believe there is a limitation on one fo the linux's
>filesystem that the time_delta is 1 seconds. That will most definitely cause
>this. In term of which filesystem it is.
The file system on the linux server is ext3.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Unfortunately the previous automated notification about the
non-inclusion of this request in Red Hat Enterprise Linux 5.3 used
the wrong text template. It should have read: this request has been
reviewed by Product Management and is not planned for inclusion
in the current minor release of Red Hat Enterprise Linux.
If you would like this request to be reviewed for the next minor
release, ask your support representative to set the next rhel-x.y
flag to "?" or raise an exception.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.