== recovery-small test 10a: finish request on server after client eviction (bug 1521) ========================================================== 13:19:47 (1743527987)
ldlm.namespaces.MGC192.168.202.120@tcp.early_lock_cancel=0
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012eaeb800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0000-osc-ffff88012eaeb800.early_lock_cancel=0
ldlm.namespaces.lustre-OST0001-osc-ffff88012eaeb800.early_lock_cancel=0
fail_loc=0x305
fail_loc=0
fail_val=0
ldlm.namespaces.MGC192.168.202.120@tcp.early_lock_cancel=1
ldlm.namespaces.lustre-MDT0000-mdc-ffff88012eaeb800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0000-osc-ffff88012eaeb800.early_lock_cancel=1
ldlm.namespaces.lustre-OST0001-osc-ffff88012eaeb800.early_lock_cancel=1
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 4028: /mnt/lustre/recon: Input/output error
Connected clients: oleg220-client.virtnet
/mnt/lustre has perms 0777 OK
[  425.563177] Lustre: ll_ost00_001: service thread pid 8300 was inactive for 40.125 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one.
[  420.187195] Lustre: mdt00_004: service thread pid 10767 was inactive for 40.069 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[  492.446620] Lustre: ll_ost00_003: service thread pid 8654 completed after 112.002s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  492.446198] Lustre: ll_ost00_000: service thread pid 8299 completed after 112.001s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  492.445918] Lustre: ll_ost00_001: service thread pid 8300 completed after 107.007s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).
[  492.202406] Lustre: mdt00_004: service thread pid 10767 completed after 112.085s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources).