thank you very much by its sincere and fast answer.
On Tue, Apr 15, 2008 at 2:26 PM, Shawn Hood <[EMAIL PROTECTED]> wrote:
> I hate to break it to you, but this kind of message isn't going to get
> you anywhere. I can assure you that many who read this message are
> thinking RTFM (see http://en.
Only one node is phisically connected, at this moment (this might change in the
future).
I was able to create a logical volume and mount it locally, so I assume
everything was correctly connected. Am I wrong?
Thank you.
- Original Message
From: John Ruemker <[EMAIL PROTECTED]>
To: lin
The gnbd approach seems to fit, although don't quite undestand why this
approach is better than the one I started with.
However, I upgraded to kernel 2.6.24, cluster-2.03.00, ais, ... and followed
instructions described in doc/min-gfs.txt in
ftp://sources.redhat.com/pub/cluster/releases/cl
I hate to break it to you, but this kind of message isn't going to get
you anywhere. I can assure you that many who read this message are
thinking RTFM (see http://en.wikipedia.org/wiki/RTFM). You're going
to have to hit the books like the rest of us.
Shawn Hood
2008/4/15 Lexi Herrera <[EMAIL P
When you say you want to share storage with the other 2 nodes, do you
mean only one node is physically connected to the storage and exports it
to the other 2? Or do you mean that all three nodes are connected to
the same storage and they share the device?
If the former, gnbd is probably wha
hi everybody, i am new in my job and new in linux and not have enough
experience with this installations, i know solaris, but don't worry. I need
install a high performance cluster with red hat enterprise and the
information that i knows is this:
- red hat enterprise as 4.5
- to
Did you setup the node with the storage as a gnbd server and the other
nodes as gnbd clients? I think this is what you want in order for the
nodes to all have block level access to the storage for clvmd and dlm to
run on top of.
-A
--
Andrew A. Neuschwander, RHCE
Linux Systems/Software Engineer
C
Hi Lon
Thans again, but that's strange because in the man , the recommended
values are :
intervall="1" tko="10" and so we have a result < 21s which is the
default value of heart-beat timer, so not a hair above like you
recommened in previous email ...
extract of man qddisk :
interval="1"