Description of problem: Saw these extra debug messages while running clustat during recovery: [root@taft-01 ~]# clustat Member Status: Quorate Member Name Status ------ ---- ------ taft-01 Online, Local, rgmanager taft-02 Online, rgmanager taft-03 Online, rgmanager taft-04 Online, rgmanager Service Name Owner (Last) State ------- ---- ----- ------ ----- GFS1 taft-02 started GFS2 taft-01 started logman taft-01 started GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM Lock: null_lk_drop_lock_req called GuLM: null_nodechange called GuLM: null_nodechange called Version-Release number of selected component (if applicable): [root@taft-02 ~]# rpm -q rgmanager rgmanager-1.9.44-0
Created attachment 123632 [details] Fixes problem
fixes in CVS - head, STABLE, RHEL4
The patch does not fix stuff in gulm-lock.c...
Created attachment 123794 [details] Cleans up lock calls