[LU-1960] Test failure on test suite sanity-benchmark, subtest test_bonnie Created: 17/Sep/12  Updated: 04/Nov/13  Resolved: 04/Nov/13

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0, Lustre 2.4.0, Lustre 2.5.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Fixed Votes: 0
Labels: performance, zfs

Issue Links:
Related
is related to LU-2887 sanity-quota test_12a: slow due to ZF... Resolved
Severity: 3
Rank (Obsolete): 4286

 Description   

This issue was created by maloo for Li Wei <liwei@whamcloud.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/556879de-fedf-11e1-b4cd-52540035b04c.

The sub-test test_bonnie failed with the following error:

test failed to respond and timed out

I didn't find anything interesting in the logs.

Info required for matching: sanity-benchmark bonnie



 Comments   
Comment by Nathaniel Clark [ 22/Jul/13 ]

I believe this is another zfs performance issue a la LU-2887.

The completion times for this test when it passes on ZFS are in the range 1800-3400 which out-lairs on either side, so those that timeout are just running long and no a failure per se.

Comment by Jian Yu [ 20/Aug/13 ]

Lustre Build: http://build.whamcloud.com/job/lustre-b2_4/33/
FSTYPE=zfs

sanity-benchmark test_bonnie also hit the same failure:
https://maloo.whamcloud.com/test_sets/82f29600-095b-11e3-ad8a-52540035b04c

Comment by Jian Yu [ 01/Nov/13 ]

Lustre Build: http://build.whamcloud.com/job/lustre-b2_4/46/
FSTYPE=zfs

sanity-benchmark test_bonnie also hit the same failure:
https://maloo.whamcloud.com/test_sets/f407fb0c-305a-11e3-b28a-52540035b04c

We'll see whether the timeout failure can disappear after TEI-790 is resolved.

Comment by Jian Yu [ 04/Nov/13 ]

Lustre Build: http://build.whamcloud.com/job/lustre-b2_4/47/
FSTYPE=zfs

With OSTCOUNT=2, sanity-benchmark test bonnie passed:
https://maloo.whamcloud.com/test_sets/51ec0c9c-444f-11e3-8472-52540035b04c

Let's close this ticket.

Generated at Sat Feb 10 01:21:11 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.