== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 09:22:38 (1773235358)
ldlm.namespaces.lustre-MDT0000-mdc-ffff8ef450f34000.lru_max_age=3900s
console_ratelimit=0
ldlm.namespaces.MGC192.168.202.146@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff8ef450f34000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff8ef450f34000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff8ef450f34000.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.202.146@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff8ef450f34000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff8ef450f34000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff8ef450f34000.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4164: /mnt/lustre/recon: Input/output error
Connected clients: oleg246-client.virtnet
/mnt/lustre has perms 0777 OK
[  549.895991] Lustre: ll_ost00_001: service thread pid 6926 was inactive for 43.039 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  549.856253] Lustre: ll_ost00_002: service thread pid 6927 was inactive for 42.998 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  545.760167] Lustre: mdt00_003: service thread pid 6369 was inactive for 40.619 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  616.973972] Lustre: mdt00_003: service thread pid 6369 completed after 111.833s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
ldlm.namespaces.lustre-MDT0000-mdc-ffff8ef450f34000.lru_max_age=600000
console_ratelimit=1