[dm-devel] [PATCH 39/39] libmultipath: increase log level of limiting dev_loss_tmo
mwilck at suse.com
mwilck at suse.com
Thu Jul 9 10:19:52 UTC 2020
From: Martin Wilck <mwilck at suse.com>
Users who aren't familar with the complex dependencies between
dev_loss_tmo, no_path_retry, and fast_io_fail may be confused
if their settings aren't applied. Print this log message at the
default level.
Signed-off-by: Martin Wilck <mwilck at suse.com>
---
libmultipath/discovery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libmultipath/discovery.c b/libmultipath/discovery.c
index c00af7e..e26aae2 100644
--- a/libmultipath/discovery.c
+++ b/libmultipath/discovery.c
@@ -651,7 +651,7 @@ sysfs_set_rport_tmo(struct multipath *mpp, struct path *pp)
}
} else if (mpp->dev_loss > DEFAULT_DEV_LOSS_TMO &&
mpp->no_path_retry != NO_PATH_RETRY_QUEUE) {
- condlog(3, "%s: limiting dev_loss_tmo to %d, since "
+ condlog(2, "%s: limiting dev_loss_tmo to %d, since "
"fast_io_fail is not set",
rport_id, DEFAULT_DEV_LOSS_TMO);
mpp->dev_loss = DEFAULT_DEV_LOSS_TMO;
--
2.26.2
More information about the dm-devel
mailing list