[LU-3813] Interop 2.4<->2.5 failure on test suite sanity test_102b: stripe count 6 != 7 Created: 21/Aug/13  Updated: 22/Dec/17  Resolved: 22/Dec/17

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

server: lustre-master build #1627
client: 2.4.0


Severity: 3
Rank (Obsolete): 9854

 Description   

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

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/bfe9f440-09ec-11e3-ad93-52540035b04c.

The sub-test test_102b failed with the following error:

stripe count 6 != 7

Info required for matching: sanity 102b



 Comments   
Comment by Sarah Liu [ 21/Aug/13 ]

test logs:

== sanity test 102b: getfattr/setfattr for trusted.lov EAs ============== 20:08:25 (1376968105)
get/set/list trusted.lov xattr ...
trusted.lov=0s0AvRCwEAAACDAQAAAAAAAHEbAAACAAAAAAABAAcAAAB8EQAAAAAAAAAAAAAAAAAAAAAAAAEAAACfEQAAAAAAAAAAAAAAAAAAAAAAAAIAAACxEQAAAAAAAAAAAAAAAAAAAAAAAAMAAABOEQAAAAAAAAAAAAAAAAAAAAAAAAQAAACdEQAAAAAAAAAAAAAAAAAAAAAAAAUAAACKEQAAAAAAAAAAAAAAAAAAAAAAAAYAAAAkDwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
 sanity test_102b: @@@@@@ FAIL: stripe count 6 != 7 
Comment by Andreas Dilger [ 23/Aug/13 ]

This is an acceptable failure condition, if one of the OSTs is full, or if it is slow and has run out of precreated objects. It might relate to the "OST full" problem in LU-3633, but I'm currently unable to bring up the maloo results.

The test should be fixed to verify the stripe count to be at least:

        [ $stripe_count -ge $((STRIPE_COUNT * 3 / 4 + 1)) ]
Comment by Andreas Dilger [ 22/Dec/17 ]

Close old bug that has not been seen in a long time.

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