[LU-2135] Test failure on test suite sanityn, subtest test_34

Sun, 10 Dec 2017 08:54:22 +0000

This issue was created by maloo for yujian <yujian@whamcloud.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/d2dceea4-12a8-11e2-bd97-52540035b04c.

Lustre Tag: v2_3_0_RC2
Lustre Build: http://build.whamcloud.com/job/lustre-b2_3/32
Distro/Arch: RHEL6.3/x86_64

The sub-test test_34 failed with the following error:

test failed to respond and timed out

Info required for matching: sanityn 34

The suite_stdout log showed that:

02:30:22:== sanityn test 33a: commit on sharing, cross crete/delete, 2 clients, benchmark == 02:30:18 (1349775018)
<~snip~>
03:06:27:=== START createmany old: 0 transaction
03:06:27:CMD: client-27vm2.lab.whamcloud.com,client-27vm1 createmany -o /mnt/lustre/d0.sanityn/d33-\$(hostname)-3/f- -r /mnt/lustre2/d0.sanityn/d33-\$(hostname)-3/f- 10000 > /dev/null 2>&1
03:30:43:********** Timeout by autotest system **********03:32:05:CMD: client-27vm7 lctl get_param -n osd*.lustre-MDT0000.mntdev

But the suite_log showed that test 33a passed but test 34 hung:

PASS 33a (3700s)

== sanityn test 34: no lock timeout under IO == 03:31:57 (1349778717)
CMD: client-27vm8 lctl get_param -n ldlm.namespaces.filter-*.lock_timeouts
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
CMD: client-27vm8 lctl set_param fail_loc=0x512
fail_loc=0x512
lock should not expire
writing on client1
reading on client2

Whamcloud Community JIRA

[LU-2135] Test failure on test suite sanityn, subtest test_34