== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 01:12:28 (1788844348)
ldlm.namespaces.lustre-MDT0000-mdc-ffff893611886000.lru_max_age=3900s
console_ratelimit=0
ldlm.namespaces.MGC192.168.201.130@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff893611886000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff893611886000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff893611886000.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.201.130@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff893611886000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff893611886000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff893611886000.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4341: /mnt/lustre/recon: Input/output error
Connected clients: oleg130-client.virtnet
/mnt/lustre has perms 0777 OK
[  709.599414] Lustre: mdt00_003: service thread pid 7362 was inactive for 41.514 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  781.971103] Lustre: mdt00_003: service thread pid 7362 completed after 113.886s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
ldlm.namespaces.lustre-MDT0000-mdc-ffff893611886000.lru_max_age=600000
console_ratelimit=1