[LU-17968] sanity-hsm test_35: mv f35.sanity-hsm-1 f35.sanity-hsm failed

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Labels: easy
• Severity: 3
• Assignee: Fred Dilger
• Reporter: Maloo

Description

This issue was created by maloo for Andreas Dilger <[e-mail]>

This issue relates to the following test suite run:
https://testing.whamcloud.com/test_sets/3feceae7-7c21-4445-ac43-f396a18e5395 (most recent)
https://testing.whamcloud.com/test_sets/6f033853-88db-43aa-8411-86ebb4d9d376 (oldest)

test_35 failed with the following error:

/usr/lib64/lustre/tests/sanity-hsm.sh: line 2714: 421072 Killed                  timeout --signal=KILL 1 mv "$f1" "$f"
mv /mnt/lustre/d35.sanity-hsm/f35.sanity-hsm-1 /mnt/lustre/d35.sanity-hsm/f35.sanity-hsm failed

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

This has been failing very intermittently since at least 2021-07-25, maybe 1/1300 runs per month.

        # mv must not block during restore
        timeout --signal=KILL 1 mv "$f1" "$f" || error "mv $f1 $f failed"

Increasing the timeout from 1s to 2s would probably avoid this rare failure (very likely due to occasional slow VM behavior) and not invalidate the test functionality.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-hsm test_35 - mv /mnt/lustre/d35.sanity-hsm/f35.sanity-hsm-1 /mnt/lustre/d35.sanity-hsm/f35.sanity-hsm failed