When processing the list of requests that have aged out, if the
request cannot be found in the store, removing it from the index. If
that is not done, Lustre will try again to remove it, leading to an
endless cycle of cancellation.
This fixes the repetition of these messages:
LustreError:
2028:0:(mdt_coordinator.c:1465:mdt_hsm_update_request_state())
tas01-MDT0000: Cannot find running request for cookie 0x54249515 on
fid=[0x200000404:0x15caa:0x0]
LustreError:
2028:0:(mdt_coordinator.c:1465:mdt_hsm_update_request_state())
Skipped
15979999 previous similar messages
LustreError: 2028:0:(mdt_coordinator.c:339:mdt_coordinator_cb())
tas01-MDT0000: Cannot cleanup timeouted request:
[0x200000404:0x15caa:0x0] for cookie 0x54249515 action=CANCEL
LustreError: 2028:0:(mdt_coordinator.c:339:mdt_coordinator_cb())
Skipped
15979999 previous similar messages
Change-Id: Ie7a2a98be8cc97db9af7a64476c06fc7321544eb
Signed-off-by: frank zago <fzago@cray.com>
Reviewed-on: http://review.whamcloud.com/12142
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: Faccini Bruno <bruno.faccini@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>