summaryrefslogtreecommitdiff
path: root/fs/dlm
diff options
context:
space:
mode:
authorGang He <ghe@suse.com>2017-05-18 05:42:12 +0300
committerDavid Teigland <teigland@redhat.com>2017-08-07 19:23:09 +0300
commit8e1743748b7e967f4dc532e3969963e5175e6f30 (patch)
treee1a18bee00fdda5c1b70cf9d76b5a441e376d9c0 /fs/dlm
parent8286d6b14c7c0e2c52d565a8727f6028a487fcf0 (diff)
downloadlinux-8e1743748b7e967f4dc532e3969963e5175e6f30.tar.xz
dlm: Make dismatch error message more clear
This change will try to make this error message more clear, since the upper applications (e.g. ocfs2) invoke dlm_new_lockspace to create a new lockspace with passing a cluster name. Sometimes, dlm_new_lockspace return failure while two cluster names dismatch, the user is a little confused since this line error message is not enough obvious. Signed-off-by: Gang He <ghe@suse.com> Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'fs/dlm')
-rw-r--r--fs/dlm/lockspace.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
index 91592b75c309..323341661d08 100644
--- a/fs/dlm/lockspace.c
+++ b/fs/dlm/lockspace.c
@@ -455,7 +455,8 @@ static int new_lockspace(const char *name, const char *cluster,
if (dlm_config.ci_recover_callbacks && cluster &&
strncmp(cluster, dlm_config.ci_cluster_name, DLM_LOCKSPACE_LEN)) {
- log_print("dlm cluster name %s mismatch %s",
+ log_print("dlm cluster name '%s' does not match "
+ "the application cluster name '%s'",
dlm_config.ci_cluster_name, cluster);
error = -EBADR;
goto out;