r737i3n0.ldebug.ping2.gz
[LU-7397] host can't lclt ping itself failed to ping 10.153.10.186@o2ib: Input/output error Created: 05/Nov/15 Updated: 14/Jul/16 Resolved: 14/Jul/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Mahmoud Hanafi | Assignee: | Doug Oucharek (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
r737i3n0.ldebug.ping2.gz
|
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
The client has go into a state where it can't be lctl ping even from it self. r737i3n0 ~ # lctl clear;lctl mark;lctl ping 10.153.10.186@o2ib;lctl mark;lctl dk /nobackupnfs2/mhanafi/r737i3n0.ldebug.ping2 Uploaded debug logs (r737i3n0.ldebug.ping2.gz) |
| Comments |
| Comment by Doug Oucharek (Inactive) [ 05/Nov/15 ] |
|
Is this problem repeatable or was it a one-off occurrence? |
| Comment by Mahmoud Hanafi [ 05/Nov/15 ] |
|
There are a number of node in this state. Some clear up but not others. Not sure what gets them into this state. I turn on some debugging to capture when it first gets into this state. |
| Comment by Mahmoud Hanafi [ 14/Jul/16 ] |
|
Unable to reproduce. Please close |
| Comment by Peter Jones [ 14/Jul/16 ] |
|
ok - thanks Mahmoud |