ping
echo reply ;)
On 10/14/2015 02:10 PM, Thomas Lamprecht wrote:
Hi,
On 10/08/2015 10:57 AM, Jan Friesse wrote:
Hi,
Thomas Lamprecht napsal(a):
[snip]
Hello,
we are using corosync version needle (2.3.5) for our cluster
filesystem
(pmxcfs).
The situation is the following. First we
ping
On 10/14/2015 02:10 PM, Thomas Lamprecht wrote:
Hi,
On 10/08/2015 10:57 AM, Jan Friesse wrote:
Hi,
Thomas Lamprecht napsal(a):
[snip]
Hello,
we are using corosync version needle (2.3.5) for our cluster
filesystem
(pmxcfs).
The situation is the following. First we start up the pmxcfs,
Hi,
again thanks for the response!
Thomas,
Thomas Lamprecht napsal(a):
Hi,
thanks for the response!
I added some information and clarification below.
On 10/01/2015 09:23 AM, Jan Friesse wrote:
Hi,
Thomas Lamprecht napsal(a):
Hello,
we are using corosync version needle (2.3.5) for our
Thomas,
Thomas Lamprecht napsal(a):
Hi,
thanks for the response!
I added some information and clarification below.
On 10/01/2015 09:23 AM, Jan Friesse wrote:
Hi,
Thomas Lamprecht napsal(a):
Hello,
we are using corosync version needle (2.3.5) for our cluster filesystem
(pmxcfs).
The
Hi,
Thomas Lamprecht napsal(a):
Hello,
we are using corosync version needle (2.3.5) for our cluster filesystem
(pmxcfs).
The situation is the following. First we start up the pmxcfs, which is
an fuse fs. And if there is an cluster configuration, we start also
corosync.
This allows the
Hello,
we are using corosync version needle (2.3.5) for our cluster filesystem
(pmxcfs).
The situation is the following. First we start up the pmxcfs, which is
an fuse fs. And if there is an cluster configuration, we start also
corosync.
This allows the filesystem to exist on one node