[LU-16924] sanity-compr test_56ba: lfs find --component-count 0 - 0 != 10 files Created: 23/Jun/23  Updated: 26/Jun/23  Resolved: 26/Jun/23

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: None
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-16904 initial test script to run sanity.sh ... In Progress
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

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

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/24922969-cde5-4abd-8dfd-88bc1571d1e4

test_56ba failed with the following error:

lfs find --component-count 0 - 0 != 10 files

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/95735 - 4.18.0-425.10.1.el8_7.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/95735 - 4.18.0-425.10.1.el8_lustre.x86_64

When system is configured with "lfs setstripe -E eof -c 1 $MOUNT", sanity test_56ba failed as

lfs find --component-count 0 - 0 != 10 files

We need to either skip this part of code when layout is set or change the test condition

# Remember non-composite files have a component count of zero
        local nfiles=$($LFS find --component-count 0 --type f $dir | wc -l)
        [[ $nfiles == 10 ]] ||
                error "lfs find --component-count 0 - $nfiles != 10 files"

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-compr test_56ba - lfs find --component-count 0 - 0 != 10 files



 Comments   
Comment by Andreas Dilger [ 23/Jun/23 ]

I think in this case, it makes sense to have the test explicitly create the plain layout files, since that is what it is looking for:

        # Create non-composite files
-       createmany -o $dir/${tfile}- 10
+       lfs setstripe -c 1 $dir/$tfile-{1..10}
Comment by Sarah Liu [ 26/Jun/23 ]

Will combine the fix in LU-16904

Generated at Sat Feb 10 03:31:08 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.