On 11/5/19 3:07 AM, Ken Gaillot wrote:
> Hi all,
>
> A reminder: We are still interested in ideas for talks, and rough
> estimates of potential attendees. "Maybe" is perfectly fine at this
> stage. It will let us negotiate hotel rates and firm up the location
> details.
Maybe we (Proxmox) could a
Hi,
Am 04/25/2018 um 09:57 AM schrieb Jan Friesse:
Thomas Lamprecht napsal(a):
On 4/24/18 6:38 PM, Jan Friesse wrote:
On 4/6/18 10:59 AM, Jan Friesse wrote:
Thomas Lamprecht napsal(a):
Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
I've tested it too and yes, you are 100% right. B
Honza,
On 4/24/18 6:38 PM, Jan Friesse wrote:
>> On 4/6/18 10:59 AM, Jan Friesse wrote:
>>> Thomas Lamprecht napsal(a):
>>>> Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
>>>>> I've tested it too and yes, you are 100% right. Bug is there and it&
Hi Honza
On 4/6/18 10:59 AM, Jan Friesse wrote:
> Thomas Lamprecht napsal(a):
>> Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
>>> I've tested it too and yes, you are 100% right. Bug is there and it's
>>> pretty easy to reproduce when node with lowest nodei
Hi Honza,
Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
Thomas,
TotemConfchgCallback: ringid (1.1436)
active processors 3: 1 2 3
EXIT
Finalize result is 1 (should be 1)
Hope I did both test right, but as it reproduces multiple times
with testcpg, our cpg usage in our filesystem, this seems
Hi,
On 3/9/18 5:26 PM, Jan Friesse wrote:
> ...
>
>> TotemConfchgCallback: ringid (1.1436)
>> active processors 3: 1 2 3
>> EXIT
>> Finalize result is 1 (should be 1)
>>
>>
>> Hope I did both test right, but as it reproduces multiple times
>> with testcpg, our cpg usage in our filesystem, this s
Hi,
On 3/7/18 1:41 PM, Jan Friesse wrote:
> Thomas,
>
>> First thanks for your answer!
>>
>> On 3/7/18 11:16 AM, Jan Friesse wrote:
first some background info for my questions I'm going to ask:
We use corosync as a basis for our distributed realtime configuration
file system (pmxcf
First thanks for your answer!
On 3/7/18 11:16 AM, Jan Friesse wrote:
> Thomas,
>
>
>> Hi,
>>
>> first some background info for my questions I'm going to ask:
>> We use corosync as a basis for our distributed realtime configuration
>> file system (pmxcfs)[1].
>
> nice
>
>>
>> We got some report
Hi,
first some background info for my questions I'm going to ask:
We use corosync as a basis for our distributed realtime configuration
file system (pmxcfs)[1].
We got some reports of a completely hanging FS with the only
correlations being high load, often IO, and most times a message that
coros
On 09/20/2016 12:36 PM, Christine Caulfield wrote:
On 20/09/16 10:46, Thomas Lamprecht wrote:
Hi,
when I'm using corosync-quorumtool [-l] and have my ring0_addr set to a
IP address,
which does not resolve to a hostname, I get the nodes IP addresses for
the 'Name' column.
A
Hi,
when I'm using corosync-quorumtool [-l] and have my ring0_addr set to a
IP address,
which does not resolve to a hostname, I get the nodes IP addresses for
the 'Name' column.
As I'm using the nodelist.node.X.name key to set the name of a node it
seems a bit confusing
to me that not this o
Thanks for the fast reply :)
On 07/25/2016 03:51 PM, Christine Caulfield wrote:
On 25/07/16 14:29, Thomas Lamprecht wrote:
Hi all,
I'm currently testing the new features of corosync 2.4, especially
qdevices.
First tests show quite nice results, like having quorum on a single node
left o
Hi all,
I'm currently testing the new features of corosync 2.4, especially qdevices.
First tests show quite nice results, like having quorum on a single node
left out of a three node cluster.
But what I'm a bit worrying about is what happens if the server where
qnetd runs, or the qdevice daem
On 16.03.2016 18:51, Tim Walberg wrote:
> Is there a way to make this work properly without STONITH? I forgot to mention
> that both nodes are virtual machines (QEMU/KVM), which makes STONITH a minor
> challenge. Also, since these symptoms occur even under "pcs cluster standby",
> where STONITH *
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,
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,
which is
an fuse fs. And if there is an cluster
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
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 situation is the following. First we start
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 'cluster
19 matches
Mail list logo
