[LU-17350] quiet spurious early-mount messages on servers Created: 08/Dec/23  Updated: 09/Dec/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Andreas Dilger Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: easy

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

There are a few messages printed early during module loading and mount that are just noise and could be quieted if the filesystem is just being mounted.

For example:

LustreError: 137-5: lustrevm-MDT0000_UUID: not available for connect
         from 0@lo (no target). If you are running an HA pair check that the target
        is mounted on the other server.

this is expected if the lnet/ptlrpc modules have loaded, but MDT0000 is not yet started.

Probably the right solution here is to add a global variable that holds the time that the module was first loaded (maybe in obdclass?) and then conditionally quiet this (and some other) messages if, say, less than RECONNECT_DELAY_MAX seconds have elapsed since the module was first loaded.

Lustre: srv-testfs-MDT0001: No data found on store. Initialize space: rc = -61

The "-61 = -ENODATA" error code is expected in this case, and is the only error that could be seen in this case, so ": rc = -61" should just be removed from the message.


Generated at Sat Feb 10 03:34:43 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.