== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 23:41:28 (1721878888)
ldlm.namespaces.MGC192.168.204.145@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012a6d8000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff88012a6d8000.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff88012a6d8000.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.204.145@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012a6d8000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff88012a6d8000.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff88012a6d8000.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4061: /mnt/lustre/recon: Input/output error
Connected clients: oleg445-client.virtnet
/mnt/lustre has perms 0777 OK
[  398.578502] Lustre: ll_ost00_005: service thread pid 19577 was inactive for 40.095 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  393.586500] Lustre: ll_ost00_001: service thread pid 8738 was inactive for 40.096 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  393.586495] Lustre: ll_ost00_003: service thread pid 11295 was inactive for 40.096 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  392.946523] Lustre: mdt00_003: service thread pid 8789 was inactive for 40.052 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  465.520628] Lustre: ll_ost00_003: service thread pid 11295 completed after 112.030s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  465.516026] Lustre: ll_ost00_001: service thread pid 8738 completed after 112.026s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  465.515866] Lustre: ll_ost00_005: service thread pid 19577 completed after 107.033s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  464.971928] Lustre: mdt00_003: service thread pid 8789 completed after 112.078s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).