[LU-11771] bad output in target_handle_reconnect: Recovery already passed deadline 71578:57

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.13.0, Lustre 2.12.3
• Severity: 3
• Assignee: James A Simmons
• Reporter: Sergey Cheremencev

Description

In functions target_handle_reconnect and target_handle_connect I've found incorrect using of linux kernel time types.

       now = ktime_get_seconds();
        deadline = jiffies_to_msecs(target->obd_recovery_timer.expires) /
                   MSEC_PER_SEC; 

Comparing jiffies converted to seconds and seconds from CLOCK_MONOTONIC is incorrect.
jiffies converted to seconds should be used Instead of ktime_get_seconds.
In this way we can avoid wrong timeouts in warnings and incorrect timeouts comparing.

2018-07-31 18:51:46 [ 8201.235800] Lustre: fs1-OST0000: Recovery already passed deadline 71578:57. If you do not want to wait more, please abort the recovery by force.
...
2018-07-31 18:51:46 [ 8201.236177] Lustre: fs1-OST0000: Denying connection for new client 71f8ec29-a676-0a96-3d1d-97b43c72e168(at 172.18.1.101@o2ib), waiting for 13 known clients (1 recovered, 11 in progress, and 1 evicted) to recover in 71578:57

Issue Links

• is related to: LU-12769 replay-dual test 0b hangs in client mount
• is related to: LU-11762 replay-single test 0d fails with 'post-failover df failed'
• is related to: LU-9019 Migrate lustre to standard 64 bit time kernel API