== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 00:56:13 (1780808173)
ldlm.namespaces.lustre-MDT0000-mdc-ffff92f783eab800.lru_max_age=3900s
console_ratelimit=0
ldlm.namespaces.MGC192.168.203.136@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff92f783eab800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff92f783eab800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff92f783eab800.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.203.136@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff92f783eab800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff92f783eab800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff92f783eab800.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4247: /mnt/lustre/recon: Input/output error
Connected clients: oleg336-client.virtnet
/mnt/lustre has perms 0777 OK
[  484.320130] Lustre: ll_ost00_004: service thread pid 14423 was inactive for 43.002 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  480.224118] Lustre: ll_ost00_003: service thread pid 7111 was inactive for 44.020 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  476.128115] Lustre: mdt00_000: service thread pid 5759 was inactive for 40.673 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  547.332861] Lustre: mdt00_000: service thread pid 5759 completed after 111.878s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
ldlm.namespaces.lustre-MDT0000-mdc-ffff92f783eab800.lru_max_age=600000
console_ratelimit=1