[LU-11733] sanity-lfsck: 'Timeout occurred after 250 mins, last suite running was sanity-lfsck

Tue, 9 Jun 2020 13:21:04 +0000

This issue was created by maloo for ablagodarenko <c17828@cray.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/adaceaf6-f804-11e8-b67f-52540065bddc

Test log:

== sanity-lfsck test 31e: Re-generate the lost slave LMV EA for striped directory (1) ================ 17:22:38 (1543944158)
#####
For some reason, the slave MDT-object of the striped directory
may lost its slave LMV EA. The LFSCK should re-generate the
slave LMV EA.
#####
Inject failure stub on MDT0 to simulate the case that the
slave MDT-object (that resides on the same MDT as the master
MDT-object resides on) lost the LMV EA.
CMD: trevis-68vm7 /usr/sbin/lctl set_param fail_loc=0x162a fail_val=0
fail_loc=0x162a
fail_val=0
CMD: trevis-68vm7 /usr/sbin/lctl set_param fail_loc=0x0 fail_val=0
fail_loc=0x0
fail_val=0
Trigger namespace LFSCK to re-generate slave LMV EA
CMD: trevis-68vm7 /usr/sbin/lctl lfsck_start -M lustre-MDT0000 -t namespace -r -A
Started LFSCK on the device lustre-MDT0000: scrub namespace
CMD: trevis-68vm7 /usr/sbin/lctl lfsck_query -t namespace -M lustre-MDT0000 -w |
		      awk '/^namespace_mdts_completed/ { print \$2 }'

Whamcloud Community JIRA

[LU-11733] sanity-lfsck: 'Timeout occurred after 250 mins, last suite running was sanity-lfsck