Hi,
I have question regarding a network partition in a 2 node cluster.
Consider a 2-node cluster (node1 and node2) setup with a cross-cable for
heartbeat and setup to use HP iLO as the fencing mechanism. In the event of
network partition (and this case assume that the cross cable was pulled out)
Hi,
I have question regarding a network partition in a 2 node cluster.
Consider a 2-node cluster (node1 and node2) setup with a cross-cable for
heartbeat and setup to use HP iLO as the fencing mechanism. In the event of
network partition (and this case assume that the cross cable was pulled out)
`gfs_tool -y` is available in 6.1.18, which is what I'm running.
On Mon, Feb 23, 2009 at 11:37 PM, Stewart Walters wrote:
> Sorry in advance, if I broke some etiquette rules of list cross posting!!
> -
> Posted to linux-clust
- "Stewart Walters" wrote:
| I've just had a GFS volume massively corrupt itself.
(snip)
| Is there any way for the user to say "Yes to all"?
|
| At least if the default choice was "Yes" when the Enter key was
| pressed, the user
| could hold down the Enter key until the entire list of blocks
Sorry in advance, if I broke some etiquette rules of list cross posting!!
-
Posted to linux-cluster and cluster-devel only because I saw a previous email
that did this also and it seemed to make sense, given the nature of the r
Kirill Kuvaldin wrote:
What are the practical/theoretical limits for number of nodes for
shared disk file systems like ocfs2/gfs2?
Theoretical limit is around 254 or so. Practical limit depends on
the hardware. Meaning, you cannot just add nodes. You have to
ensure the interconnect and the stor
Alright, more testing today.
I reconfigured the GFS nodes to export the filesystems using NFS4 and
adjusted the client mounts accordingly and BAM! everything worked,
even firefox which was also killing me. So it seems this is a
GFS2+NFS3 thing. I did have to, as previously noted, shrink my wsize
d
The cluster team and its community are proud to announce the
3.0.0.alpha5 release from the STABLE3 branch.
The development cycle for 3.0.0 is about to end. With the new STABLE3
branch that will collect only bug fixes and minimal update required to
build on top of the latest upstream kernel, we are
