Bruce,
[root@client1-ci-291117203803930 nfs4.1]# ./testserver.py 172.29.53.145:/ --verbose --outfile=/tmp/pynfs4.1.out --minorversion=2 --maketree RNM14
Could not find gssapi module, proceeding without
INFO :rpc.poll:got connection from ('127.0.0.1', 55390), assigned to fd=5
INFO :rpc.thread:Called connect(('172.29.53.145', 2049))
INFO :rpc.poll:Adding 6 generated by another thread
INFO :test.env:Created client to 172.29.53.145, 2049
INFO :test.env:Called do_readdir()
INFO :test.env:do_readdir() = []
RNM14 st_rename.testFileToDir : RUNNING
RNM14 st_rename.testFileToDir : FAILURE
RENAME file into existing dir should return
NFS4ERR_EXIST or NFS4ERR_ISDIR, instead got
NFS4ERR_SERVERFAULT
INFO :test.env:Called do_readdir()
INFO :test.env:do_readdir() = [entry4(cookie=418L, name='RNM14_1512003093', attrs={})]
INFO :test.env:Called do_readdir()
INFO :test.env:do_readdir() = [entry4(cookie=419L, name='dir', attrs={}), entry4(cookie=420L, name='file', attrs={})]
**************************************************
RNM14 st_rename.testFileToDir : FAILURE
RENAME file into existing dir should return
NFS4ERR_EXIST or NFS4ERR_ISDIR, instead got
NFS4ERR_SERVERFAULT
**************************************************
Command line asked for 1 of 280 tests
Of those: 0 Skipped, 1 Failed, 0 Warned, 0 Passed
Yet according to RFC 5661, Section 15.2 (table 6), NFS4ERR_ISDIR
is not an allowed error code for RENAME.
According to POSIX rename() it is an allowed error code. I believe
the assumption is that the client should catch this case first?
Anyway, does the knfsd return NFS4ERR_ISDIR in this test case?
Thanks,
Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
