[LU-2328] Improve "is not available for connect (no target)" message Created: 14/Nov/12 Updated: 07/Jun/16 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Prakash Surya (Inactive) | Assignee: | Alex Zhuravlev |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | shh | ||
| Rank (Obsolete): | 5560 |
| Description |
|
When a client is misconfigured, it may try to connect to an OST which does not exist. This can cause these messages on the server: LustreError: 137-5: UUID 'ls1-OST0011_UUID' is not available for connect (no target) LustreError: 137-5: UUID 'ls1-OST0012_UUID' is not available for connect (no target) LustreError: 137-5: UUID 'ls1-OST0012_UUID' is not available for connect (no target) LustreError: 137-5: UUID 'ls1-OST0011_UUID' is not available for connect (no target) If the client is never cleaned up, this will go on indefinitely. This should really be cleaned up, and a message should only be printed a single time for this type of error (to help spot mis-configured clients). For example, it would be better if the server kept a list of clients that have tried to connect to this non-existent OST, and only print a message once per client. We tend to hit this when we re-purpose our development filesystems without rebooting/remounting clients, which then clutters the server log. |
| Comments |
| Comment by Peter Jones [ 15/Nov/12 ] |
|
Alex will triage this one |