[LU-4601] Failure on test suite parallel-scale-nfsv3 test_compilebench

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Affects Version/s: Lustre 2.6.0
• Labels: patch
• Environment: client and server: lustre-master build # 1876 RHEL6 ldiskfs
• Severity: 3
• Assignee: Zhenyu Xu
• Reporter: Maloo

Description

This issue was created by maloo for sarah <[e-mail]>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/cada8aee-8e18-11e3-9383-52540035b04c.

The sub-test test_compilebench failed with the following error:

compilebench failed: 1

== parallel-scale-nfsv3 test compilebench: compilebench == 14:45:47 (1391553947)
OPTIONS:
cbench_DIR=/usr/bin
cbench_IDIRS=2
cbench_RUNS=2
client-16vm1
client-16vm2.lab.whamcloud.com
./compilebench -D /mnt/lustre/d0.compilebench -i 2         -r 2 --makej
using working directory /mnt/lustre/d0.compilebench, 2 intial dirs 2 runs
native unpatched native-0 222MB in 189.77 seconds (1.17 MB/s)
Traceback (most recent call last):
  File "./compilebench", line 567, in <module>
    dset = dataset(options.sources, rnd)
  File "./compilebench", line 319, in __init__
    self.unpatched = native_order(self.unpatched, "unpatched")
  File "./compilebench", line 104, in native_order
    os.rmdir(fullpath)
OSError: [Errno 39] Directory not empty: '/mnt/lustre/d0.compilebench/native-0'
 parallel-scale-nfsv3 test_compilebench: @@@@@@ FAIL: compilebench failed: 1 

Issue Links

• is related to: LU-4603 NFS reexport leads to problems of "ls"

Comments

[Sarah Liu]

Close this bug since didn't see it in the latest tests. The tests are failed due to LU-5109

[James A Simmons]

Is this bug still seen. Now that patch 9038 has landed it should have gone away. If this bug is not longer showing up please close this ticket.

[James A Simmons]

better yet I push a separate 9038 patch to see if it address this problem with the proper test suite string. What is the maloo test string I should push to cover the above failures?

[Cliff White (Inactive)]

bobijam, can you look at the Maloo issues?

[James A Simmons]

The problem is that one module could before another when the server/client stack is in the same node. In this case it is osc/osp. A work around could be for the test framework to load osc.ko first then osp.ko later. Also please try my 9038 patch to make sure on your end that it passes the failing test. My testing is going okay but you never know.

[Cliff White (Inactive)]

James, is there anything you can do to address the Maloo failures?

[Jian Yu]

Lustre Build: http://build.whamcloud.com/job/lustre-master/1890/

The same failure occurred:
https://maloo.whamcloud.com/test_sets/4ab871b0-9687-11e3-bc3b-52540035b04c
https://maloo.whamcloud.com/test_sets/68f2c766-9687-11e3-bc3b-52540035b04c
https://maloo.whamcloud.com/test_sets/56a578e4-9680-11e3-a009-52540035b04c
https://maloo.whamcloud.com/test_sets/68db57f4-9680-11e3-a009-52540035b04c