[LU-9507] o2iblnd assert on reconnect Created: 16/May/17 Updated: 25/Aug/17 Resolved: 29/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.10.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Doug Oucharek (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
An assert in kiblnd_reconnect_peer() is being hit. With the multi-qp patch, it is possible to have ibp_connecting to be > 0. Since one connection can fail, and an attempt to reconnect can occur, while the other connections are still being established. Discussed with Doug and this assert should be changed to an if statement, to log when this situation occurs instead of asserting. |
| Comments |
| Comment by Gerrit Updater [ 16/May/17 ] |
|
Doug Oucharek (doug.s.oucharek@intel.com) uploaded a new patch: https://review.whamcloud.com/27139 |
| Comment by Gerrit Updater [ 29/May/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/27139/ |
| Comment by Peter Jones [ 29/May/17 ] |
|
Landed for 2.10 |