Lustre recovery model rely on the fact that each request produces single transaction, meanwhile there can be multiple transactions in single requests by design or by mistakes in design. There is message about in tgt_txn_stop_cb() but it has D_HA level and contains almost no information.

I propose to increase level to D_WARNING and put more debugging info to find out what request produce that and execution context.

With more new features we start seeing such situations with multiple transaction more often, this change will help to see problem at early stage in developing and handle it properly