|
Bugzilla – Full Text Bug Listing |
| Summary: | connectathon lock tests are failing in version 3 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Anilkumar Bolleni <abolleni> |
| Component: | Other | Assignee: | Petr Ostadal <postadal> |
| Status: | VERIFIED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | forgotten_b5BnQSUi71, nfbrown, ro |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
nfs client platforms OES-Linux and Solaries Just for the record: Which version of that test did you use and where can it be downloaded? You may also attach it right here. Thanks. http://www.connectathon.org/nfstests.html download nfstests.tar.gz from this site. all set up instructions are there in this site. for any issues get back to me . Thanks. Reassinging this to the nfs-server maintainer and taking the nfs-utils maintainer into CC. Unable to reproduce the issue in SUSE Linux Professional 9.3. Just an observation. All the lock tests are passing when the tests are run against a NFSv4 mount point. i.e Manually mounting using -tnfs4 and then running the tests against the mount point. Error 116 is ESTALE. What NFS server were you using? Please provide a tcpdump (on the client, run tcpdump -w nfs.log -s0 port 2049) and a kernel NFS debug log (before starting the lock test, run echo 65535 > /proc/sys/sunrpc/nfs_debug Looks very like a known and fixed bug. Can you try a kotd kernel, or any sl-10 kernel sinze about oct 20. *** This bug has been marked as a duplicate of 128784 *** Hang on.... I just noticed that it says 'V4' in the title, and the above bug only affects v2/v3. But then the description says ./server -l -o vers=3,proto=tcp -p <export path> -m <mountpoint> <serverip> which suggests V3. Then comment 6 says it all works for V4. so which is it? If it is a V3 bug, then the above mentioned duplicate is the bug. But if it is really truely v4, then it must be a different bug with identical symptoms.. The Title is misleading. It's a V3 bug and lock tests are working for V4. comment 6 holds good. Will apply the patch provided for the Bug 128784 and will revert. Changing the title.. Neil's patch to Bug 120704 fixed the issue. Thanks Neil. closing this bug as patch to BUG 120704 has fixed the issue . now all lock tested are passed . |
OS: SUSE LINUX 10.0 RC4 STEPS: start all nfsv4 demons like rpc.idmapd rpc.mountd rpc.svcgssd rpc.nfsd run connectathon lock test on nfsv4 exported path from nfs client. ./server -l -o vers=3,proto=tcp -p <export path> -m <mountpoint> <serverip> Results: gives below error Test #1 - Test regions of an unlocked file. Parent: 1.1 - F_TEST [ 0, 1] FAILED! Parent: **** Expected success, returned errno=116... Parent: **** Probably implementation error. ** PARENT pass 1 results: 0/0 pass, 0/0 warn, 1/1 fail (pass/total). ** CHILD pass 1 results: 0/0 pass, 0/0 warn, 0/0 fail (pass/total). lock tests failed this lock tests are failed on RC1 build also.