[LU-2903] replay-ost-single test_6 and test_7 failure Created: 04/Mar/13  Updated: 30/Sep/16  Resolved: 03/Jul/13

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

Type: Bug Priority: Blocker
Reporter: Maloo Assignee: Nathaniel Clark
Resolution: Fixed Votes: 0
Labels: HB, zfs

Issue Links:
Duplicate
Related
is related to LU-2005 skip replay-ost-single test 6,7 for OFD Resolved
Severity: 3
Rank (Obsolete): 6992

 Description   

This issue was created by maloo for Hiroya Nozaki <nozaki.hiroya@jp.fujitsu.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/34b38944-8513-11e2-9ab1-52540035b04c.

The sub-test test_7 failed with the following error:

test_7 failed with 1

Info required for matching: replay-ost-single 7



 Comments   
Comment by Andreas Dilger [ 05/Mar/13 ]

It appears that test_6 is always failing before test_7 fails, so it makes sense to fix LU-2620 first before determining if this is a separate bug.

Comment by Andreas Dilger [ 05/Mar/13 ]

Actually, some tests have failed without test_6 having failed:
https://maloo.whamcloud.com/test_sets/d38fa5aa-7d36-11e2-ac80-52540035b04c

Comment by Jodi Levi (Inactive) [ 06/Mar/13 ]

Nathaniel,
Could you please have a look at this one?

Comment by Andreas Dilger [ 06/Mar/13 ]

Assign to Nathaniel, since this is failing exclusively on ZFS right now.

Comment by Nathaniel Clark [ 08/Mar/13 ]

http://review.whamcloud.com/5662

Comment by Sarah Liu [ 21/Mar/13 ]

Hit this issue in lustre-master ofed build #1328 zfs testing: https://maloo.whamcloud.com/test_sets/686b6600-9187-11e2-8eff-52540035b04c

Comment by Peter Jones [ 21/Mar/13 ]

Landed for 2.4

Comment by Nathaniel Clark [ 18/Jun/13 ]

ZFS log size allow by previous patch was not large enough:

http://review.whamcloud.com/6692

Comment by Jodi Levi (Inactive) [ 03/Jul/13 ]

Patch landed to Master. Closing ticket, please let me know if more work is needed and I will reopen the ticket.

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