== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 11:46:25 (1724773585)
ldlm.namespaces.MGC192.168.201.158@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012b779000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff88012b779000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff88012b779000.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.201.158@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012b779000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff88012b779000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff88012b779000.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4064: /mnt/lustre/recon: Input/output error
Connected clients: oleg158-client.virtnet
/mnt/lustre has perms 0777 OK
[  420.500371] Lustre: ll_ost00_004: service thread pid 18882 was inactive for 40.044 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  415.508338] Lustre: ll_ost00_003: service thread pid 10389 was inactive for 40.042 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  414.356383] Lustre: mdt00_002: service thread pid 7064 was inactive for 40.022 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  486.409135] Lustre: mdt00_002: service thread pid 7064 completed after 112.075s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).