[Pacemaker] ping_pong test fails

Uwe Ritzschke uwe.ritzschke.2 at cms.hu-berlin.de
Wed Dec 7 15:52:50 UTC 2011


Hi,

Perhaps someone can help me? I've got a problem similar to the one 
posted by Raphael on 02/22/2010 [gfs2: ping_pong test fails]:

When I'm running samba's ping_pong test on a 3-node pacemaker cluster 
with gfs2, it returns

# ./ping_pong /srv/digedag/foo 3
lock at 1 failed! - Function not implemented
unlock at 0 failed! - Function not implemented
[..]

Both dlm_controld.pcmk and gfs_controld.pcmk are running, mounting seems 
to work correctly.

Did I miss something crucial in the configuration (attached below)? I've 
read the "Clusters from Scratch" guide over and over again, but I'm a 
bit lost.

Any advice would be greatly appreciated!

Thanks,
Uwe



----Our setup----
3 nodes running
centOS 6.0
corosync 1.2.3
pacemaker 1.1.2
gfs-pcmk 3.0.12
resource-agents 3.0.12

Shared storage is a SAN

----pacemaker----
primitive digedagFS ocf:heartbeat:Filesystem \
	params device="/dev/mapper/digedag1p1" directory="/srv/digedag" 
fstype="gfs2" \
	op start interval="0" timeout="60" \
	op stop interval="0" timeout="60"
primitive dlm ocf:pacemaker:controld \
	op monitor interval="120" \
	op start interval="0" timeout="90" \
	op stop interval="0" timeout="100"
primitive gfs-control ocf:pacemaker:controld \
	params daemon="gfs_controld.pcmk" args="-g 0" \
	op monitor interval="120" \
	op start interval="0" timeout="90" \
	op stop interval="0" timeout="100"
clone digedagFSClone digedagFS
clone dlm-clone dlm \
	meta interleave="true"
clone gfs-clone gfs-control \
	meta interleave="true"
colocation digedagFS-with-gfs-control inf: digedagFSClone gfs-clone
colocation gfs-with-dlm inf: gfs-clone dlm-clone
order start-digedagFS-after-gfs-control inf: gfs-clone digedagFSClone
order start-gfs-after-dlm inf: dlm-clone gfs-clone

----/sys/log/messages----
[...]
Dec  7 16:04:14 localhost kernel: GFS2 (built Jun 27 2011 18:09:43) 
installed
Dec  7 16:04:14 localhost kernel: GFS2: fsid=: Trying to join cluster 
"lock_dlm", "pcmk:smb"
Dec  7 16:04:14 localhost kernel: dlm: Using TCP for communications
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: Joined cluster. 
Now mounting FS...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=0, already 
locked for use
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=0: Looking 
at journal...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=0: Done
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=1: Trying 
to acquire journal lock...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=1: Looking 
at journal...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=1: Done
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=2: Trying 
to acquire journal lock...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=2: Looking 
at journal...
Dec  7 16:04:14 localhost kernel: GFS2: fsid=pcmk:smb.0: jid=2: Done

----mount----
# mount | grep digedag
/dev/mapper/digedag1p1 on /srv/digedag type gfs2 
(rw,seclabel,relatime,hostdata=jid=0)







More information about the Pacemaker mailing list