summaryrefslogtreecommitdiffstats
path: root/fs/dlm
diff options
context:
space:
mode:
authorDavid Teigland <teigland@redhat.com>2008-01-16 11:03:41 -0600
committerDavid Teigland <teigland@redhat.com>2008-01-30 11:04:43 -0600
commit594199ebaae5d77f025974dfcfa6651cc81325a8 (patch)
tree35e4d61197ec8c1cbc63274a3f4e6ad37bc9a265 /fs/dlm
parentce5246b972f7514af899a63c0faf831d05ed5ee1 (diff)
downloadblackbird-op-linux-594199ebaae5d77f025974dfcfa6651cc81325a8.tar.gz
blackbird-op-linux-594199ebaae5d77f025974dfcfa6651cc81325a8.zip
dlm: change error message to debug
The invalid lockspace messages are normal and can appear relatively often. They should be suppressed without debugging enabled. Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'fs/dlm')
-rw-r--r--fs/dlm/lock.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index bc2e4ba4c1be..7ee7c7c55453 100644
--- a/fs/dlm/lock.c
+++ b/fs/dlm/lock.c
@@ -3857,8 +3857,9 @@ void dlm_receive_buffer(struct dlm_header *hd, int nodeid)
ls = dlm_find_lockspace_global(hd->h_lockspace);
if (!ls) {
- log_print("invalid h_lockspace %x from %d cmd %d type %d",
- hd->h_lockspace, nodeid, hd->h_cmd, type);
+ if (dlm_config.ci_log_debug)
+ log_print("invalid lockspace %x from %d cmd %d type %d",
+ hd->h_lockspace, nodeid, hd->h_cmd, type);
if (hd->h_cmd == DLM_RCOM && type == DLM_RCOM_STATUS)
dlm_send_ls_not_ready(nodeid, rc);
OpenPOWER on IntegriCloud