[LU-4666] Test failure on test suite sanity-scrub, subtest test_12 Created: 25/Feb/14  Updated: 12/Apr/14  Resolved: 12/Apr/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Related
is related to LU-4670 suite sanity test_222a test223: f223.... Open
Severity: 3
Rank (Obsolete): 12786

 Description   

This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/66cadd88-9dea-11e3-98f5-52540035b04c.

The sub-test test_12 failed with the following error:

(2) ls should fail

Info required for matching: sanity-scrub 12



 Comments   
Comment by Emoly Liu [ 11/Mar/14 ]

I hit this issued during testing LU-4524, after rebasing the code, this issue has gone. But in my local test, it always report another lustre error

== sanity-scrub test 12: OI scrub can rebuild invalid /O entries == 14:33:54 (1394519634)
stopall
formatall
setupall
fail_loc=0x195
total: 1000 creates in 2.66 seconds: 375.38 creates/second
stopall
setupall

Message from syslogd@centos6-2 at Mar 11 14:34:54 ...
 kernel:LustreError: 9407:0:(ofd_dev.c:1186:ofd_orphans_destroy()) lustre-OST0000: error destroying precreated id [0x100000000:0x401:0x0]: rc = -116
fail_loc=0
Resetting fail_loc on all nodes...done.
PASS 12 (71s)
Comment by James Nunez (Inactive) [ 08/Apr/14 ]

I hit this error at https://maloo.whamcloud.com/test_sets/44445f5a-bf0f-11e3-adc7-52540035b04c

Comment by nasf (Inactive) [ 08/Apr/14 ]

This issue will be fixed by the patch:

http://review.whamcloud.com/#/c/9759/

Comment by Andreas Dilger [ 12/Apr/14 ]

Hit this on https://maloo.whamcloud.com/test_sessions/fb7c66b0-c08e-11e3-ae98-52540035b04c

Comment by nasf (Inactive) [ 12/Apr/14 ]

It is because we inject failure at the test beginning, which cause some OST-object will be destroyed unexpected. I will fix related bugs in LU-4803

Comment by nasf (Inactive) [ 12/Apr/14 ]

It is another failure instance of LU-4803

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