[Ocfs2-users] errors with VMware guests

[Michael Steinmann]

We're getting errors when copying directory trees on two VMware guest
nodes sharing a SAN LV. node 1 hung after the error occured.

The nodes are SLES9 SP3 i586 VMware ESX guests using RDMs (physical disks;
not VMDKS), network is 100Mbit.

on node 0
dmesg:
OCFS2 Node Manager 1.1.7-SLES Tue Nov  1 14:45:27 PST 2005 (build sles)
OCFS2 DLM 1.1.7-SLES Tue Nov  1 14:45:27 PST 2005 (build sles)
OCFS2 DLMFS 1.1.7-SLES Tue Nov  1 14:45:27 PST 2005 (build sles)
OCFS2 User DLM kernel interface loaded
(6873,0):__dlm_print_nodes:380 Nodes in my domain
("260E7B2528F8405FAA453CFEEF57D7C1"):
(6873,0):__dlm_print_nodes:384  node 0
scsi1: Tagged Queuing now active for Target 1
scsi0: Allocated 7 additional CCBs (total now 35)
OCFS2 1.1.7-SLES Tue Nov  1 14:45:27 PST 2005 (build sles)
(6920,0):ocfs2_initialize_super:1332 max_slots for this device: 4
(6920,0):ocfs2_fill_local_node_info:1011 I am node 0
(6920,0):__dlm_print_nodes:380 Nodes in my domain
("260E7B2528F8405FAA453CFEEF57D7C1"):
(6920,0):__dlm_print_nodes:384  node 0
(6920,0):ocfs2_find_slot:262 slot 1 is already allocated to this node!
(6920,0):ocfs2_find_slot:268 taking node slot 1
(6920,0):ocfs2_check_volume:1574 File system was not unmounted cleanly,
recovering volume.
kjournald starting.  Commit interval 5 seconds
ocfs2: Mounting device (8,17) on (node 0, slot 1)
(6933,0):ocfs2_replay_journal:1167 Recovering node 1 from slot 0 on device
(8,17)
kjournald starting.  Commit interval 5 seconds
(6860,0):o2net_set_nn_state:422 accepted connection from node stvlxrep03
(num 1) at 10.2.199.10:7777
(6860,0):__dlm_print_nodes:380 Nodes in my domain
("260E7B2528F8405FAA453CFEEF57D7C1"):
(6860,0):__dlm_print_nodes:384  node 0
(6860,0):__dlm_print_nodes:384  node 1
scsi1: Allocated 7 additional CCBs (total now 35)
(7130,0):dlmlock_remote:218 ERROR: dlm status = DLM_IVLOCKID
(7130,0):dlmlock:653 ERROR: dlm status = DLM_IVLOCKID
(7130,0):ocfs2_lock_create:756 ERROR: Dlm error "DLM_IVLOCKID" while
calling dlmlock on resource M00000000000000000903e25186f9bb: bad lockid
(7130,0):ocfs2_cluster_lock:930 ERROR: status = -22
(7130,0):ocfs2_meta_lock_full:1527 ERROR: status = -22
(7130,0):ocfs2_inode_revalidate:1045 ERROR: status = -22
(7130,0):ocfs2_getattr:1108 ERROR: status = -22

syslog:
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):dlmlock_remote:218 ERROR: dlm
status = DLM_IVLOCKID
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):dlmlock:653 ERROR: dlm status
= DLM_IVLOCKID
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):ocfs2_lock_create:756 ERROR:
Dlm error "DLM_IVLOCKID" while calling dlmlock on resource
M00000000000000000903e25186f9bb: bad lockid
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):ocfs2_cluster_lock:930 ERROR:
status = -22
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):ocfs2_meta_lock_full:1527
ERROR: status = -22
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):ocfs2_inode_revalidate:1045
ERROR: status = -22
Feb  3 15:00:12 spvlxrep03 kernel: (7130,0):ocfs2_getattr:1108 ERROR:
status = -22


on node 1
Feb  3 15:01:44 stvlxrep03 kernel: (4633,0):dlm_create_lock_handler:440
ERROR: dlm status = DLM_IVLOCKID

--
mike