I have a 4 node SLES 10 cluster with all nodes attached to a SAN via
fiber.
The SAN has a EVMS volume formatted with ocfs2. Below is my ocfs2.conf.
I can mount the volume on any single node but as soon as I mount it on
the second node, it fences one of the nodes. There is never more than
one
John,
it's hard to tell without seeing the messages on the surviving node. Do
you remember how many node slots you have created when formating the
volume? Maybe you configured just 1?, if so, use tunefs.ocfs2 to
increase the number of slots
If that's not the problem, please copy paste the
1. In SLES10, the /config has been moved to /sys/kernel/config. That's
how it
is on mainline.
2. To monitor heartbeat do:
# watch -d -n2 debugfs.ocfs2 -R hb /dev/sdX
This comand will work if you have ocfs2-tools 1.2.2. (Not sure whether
sles10 ships
with 1.2.2 or 1.2.1.) If 1.2.1, do:
# watch
As I remember from the LinuxWorld, such configuration requires usingh
heartbeat2 in addition to o2cb, and configuring OCFSv2 to make heartbeat
thru it (not directly).
It's what SuSe tested:
- 4 nodes
- heartbeat2
- evms
- OCFSv2 interacting with heartbeat2
- Original Message -
From:
Hello guys,
I am doing some research here about ocfs2, I suppose it has a very bad
impact on device waiting.
could you please perform the following command and reply with your
output? this request goes out only to linux 2.6 (2.6.18 prefered)
users.
the comand is:
iostat -x
my output of the
