Interestingly enough this works! :)
Wouldnt this result in loss of performance though?
Alexei Roudnev wrote:
What if they mount the same drive on iSCSI server but using iSCSI to itself
(so it will work as both, server and client, at the same time)?
It should work fine.
----- Original Message -----
From: "Mark Fasheh" <[EMAIL PROTECTED]>
To: "Patrick Donker" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Monday, December 18, 2006 10:10 PM
Subject: Re: [Ocfs2-users] another node is heartbeating in our slot!
On Mon, Dec 18, 2006 at 11:39:49PM +0100, Patrick Donker wrote:
Now, as soon as I mount /dev/sdb on 'san' itself, I get the 'another
node is
heartbeating in our slot!' message, and the system fences all nodes,
which
results in kernel panics. Apparently 'san' is trying to heartbeat on
slot 0,
which already is occupied by 'mail'. Looking at the cluster.conf, 'san'
should
select slot 1. How come it is trying to use 0 then?
Am I correct in assuming that I cannot mount the ocfs2 fs on the system
which
is running the cluster???
Yes. The node you export the iscsi drive (your iscsi target, or 'san' in
this example) can not run ocfs2 on that drive alongside other nodes who
have
it mounted via the iscsi client. This is a limitation in that the iscsi
target does not share the same pages against the iscsi device and the
block
device.
So basically, the machine which runs the iscsi target software cannot also
run the file system. All nodes mounting it via the iscsi client should
work
fine. For what it's worth, mounting on the iscsi target alongside iscsi
targets won't work with _any_ shared disk cluster file system.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
[EMAIL PROTECTED]
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
