== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 09:40:32 (1786542032)
ldlm.namespaces.lustre-MDT0000-mdc-ffff8bdb04d25800.lru_max_age=3900s
console_ratelimit=0
ldlm.namespaces.MGC192.168.201.148@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff8bdb04d25800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff8bdb04d25800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff8bdb04d25800.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.201.148@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff8bdb04d25800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff8bdb04d25800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff8bdb04d25800.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4316: /mnt/lustre/recon: Input/output error
Connected clients: oleg148-client.virtnet
/mnt/lustre has perms 0777 OK
[  439.264136] Lustre: ll_ost00_002: service thread pid 6655 was inactive for 41.468 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  435.168119] Lustre: ll_ost00_004: service thread pid 10840 was inactive for 42.483 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  431.072118] Lustre: mdt00_004: service thread pid 8172 was inactive for 40.736 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  502.777539] Lustre: mdt00_004: service thread pid 8172 completed after 112.441s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
ldlm.namespaces.lustre-MDT0000-mdc-ffff8bdb04d25800.lru_max_age=600000
console_ratelimit=1