[LU-12252] sanity-hsm test 220A, 220a, 221, 223b, 224A, 224a, 226 fail with ‘The expected changelog was not emitted’

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.13.0, Lustre 2.12.1, Lustre 2.12.3, Lustre 2.12.4
• Labels: always_except ppc
• Environment: PPC clients
• Severity: 3
• Assignee: WC Triage
• Reporter: James Nunez (Inactive)

Description

sanity-hsm test_220A, 220a, 221, 223b, 224A, 224a, 226 fail with ‘The expected changelog was not emitted’. We see this for PPC client testing only.

Looking at the client 1 (vm1) dmesg log for a recent failure, https://testing.whamcloud.com/test_sets/82a14510-668f-11e9-8bb1-52540065bddc, we see an ‘invalid record’ message for most of these failures

[ 2678.768679] Lustre: DEBUG MARKER: == sanity-hsm test 220A: Changelog for archive ======================================================= 06:01:49 (1555999309)
[ 2681.992599] Lustre: 31712:0:(llog_cat.c:783:llog_cat_process_common()) lustre-MDT0000-mdc-c000000076f9e800: invalid record in catalog [0x5:0x0:0xa]:0: rc = -22
[ 2681.992753] LustreError: 31712:0:(mdc_changelog.c:236:chlg_load()) lustre-MDT0000-mdc-c000000076f9e800: fail to process llog: rc = -22
[ 2682.153063] Lustre: DEBUG MARKER: /usr/sbin/lctl mark  sanity-hsm test_220A: @@@@@@ FAIL: The expected changelog was not emitted 

There are no other errors seen in the dmesg and copytool logs.

Logs for other failures are at
https://testing.whamcloud.com/test_sets/0352f31e-6322-11e9-8bb1-52540065bddc
https://testing.whamcloud.com/test_sets/c3ef7fae-5f6f-11e9-9646-52540065bddc

Issue Links

• is related to: LU-12883 PPC client: lustre-rsync-test test_2a: lfs changelog: cannot access changelog: Invalid argument