Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.4.0
-
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.