[Ocfs2-users] OCFS2 ERROR: status = - 107

[David Murphy]

Last time I ran into this I had to take the cluster offline and do  fsck -fy
/dev/XXXX   this repaired the damage to the FS and the cluster was able to
start.

 

Basically it  not starting  the   cluster because it noticed a node is "out
of sync" .

 

David

 

From: ocfs2-users-bounces at oss.oracle.com
[mailto:ocfs2-users-bounces at oss.oracle.com] On Behalf Of Francesco Gabriele
Sent: Wednesday, May 26, 2010 7:38 AM
To: ocfs2-users at oss.oracle.com
Subject: [Ocfs2-users] OCFS2 ERROR: status = - 107

 

Good afternoon,
I am facing these errors on the /var/log/messages regarding ocfs:

kernel: (21371,5):dlm_drop_lockres_ref:2295 ERROR: status = -107
kernel: (21371,5):dlm_purge_lockres:189 ERROR: status = -107
kernel: (21371,5):dlm_drop_lockres_ref:2295 ERROR: status = -107
kernel: (21371,5):dlm_purge_lockres:189 ERROR: status = -107
kernel: (21371,5):dlm_drop_lockres_ref:2295 ERROR: status = -107
kernel: (21371,5):dlm_purge_lockres:189 ERROR: status = -107
kernel: (21371,5):dlm_drop_lockres_ref:2295 ERROR: status = -107
kernel: (21371,5):dlm_purge_lockres:189 ERROR: status = -107

(21312,2):dlm_get_lock_resource:966 E66ADD1149B9416E8D2B3CA50809ABE0:
recovery map is not empty, but must master $RECOVERY lock now
(10571,0):ocfs2_replay_journal:1191 Recovering node 0 from slot 0 on device
(8,17)
(10577,0):ocfs2_replay_journal:1191 Recovering node 0 from slot 0 on device
(8,113)
(10576,0):ocfs2_replay_journal:1191 Recovering node 0 from slot 0 on device
(8,97)
(10575,0):ocfs2_replay_journal:1191 Recovering node 0 from slot 0 on device
(8,81)
(21372,3):dlm_get_lock_resource:932
70984185BB314019A43246EB1EDCBEA0:$RECOVERY: at least one node (0) torecover
before lock mastery can begin
(21372,3):dlm_get_lock_resource:966 70984185BB314019A43246EB1EDCBEA0:
recovery map is not empty, but must master $RECOVERY lock now
(21360,6):dlm_get_lock_resource:932
3A7F251A33BD448690BD4967BF9EB992:$RECOVERY: at least one node (0) torecover
before lock mastery can begin
(21360,6):dlm_get_lock_resource:966 3A7F251A33BD448690BD4967BF9EB992:
recovery map is not empty, but must master $RECOVERY lock now
kernel: kjournald starting. Commit interval 5 seconds
kjournald starting. Commit interval 5 seconds


Can someone tell me what kind of error is it and which can be the cause?

Thanks.

Regards,
Francesco Gabriele 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20100526/55cc030e/attachment.html