== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 04:54:44 (1726304084)
ldlm.namespaces.MGC192.168.201.151@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff8800b5801800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff8800b5801800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff8800b5801800.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.201.151@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff8800b5801800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff8800b5801800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff8800b5801800.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4072: /mnt/lustre/recon: Input/output error
Connected clients: oleg151-client.virtnet
/mnt/lustre has perms 0777 OK
[  441.205657] Lustre: ll_ost00_004: service thread pid 18086 was inactive for 40.072 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  436.213694] Lustre: ll_ost00_003: service thread pid 10915 was inactive for 40.065 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  436.213687] Lustre: ll_ost00_001: service thread pid 8423 was inactive for 40.065 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  435.062226] Lustre: mdt00_002: service thread pid 7070 was inactive for 40.064 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  507.108562] Lustre: mdt00_002: service thread pid 7070 completed after 112.110s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).