Il 11/10/2017 21:22, Roberto Resoli ha scritto:
>> drbdmon is included in recent drbd-utils versions.
> Unfortunately is not in current (9.1.1) drbd-utils package in pve5 repo.
Sorry, I meant that *drbdtop* is not in current drbd-utils package.
bye,
rob
___
Il 05/10/2017 18:06, Robert Altnoeder ha scritto:
> On 10/05/2017 08:49 AM, Roberto Resoli wrote:
...
>> cat
>> /sys/kernel/debug/drbd/resources/${resource_name}/connections/${node_name}/0/proc_drbd
>>
>
> However, the contents and format of anything under /sys/kernel/debug is
> subject to change
Sending this message again without the attachments, as it apparently did
not make it through to the list archive.
On 10/05/2017 08:49 AM, Roberto Resoli wrote:
You can use this for "old-style" monitoring of drbd9 connections to
${node_name}, related to ${resource_name}:
cat
/sys/kernel/debug/d
Il 05/10/2017 10:19, Martyn Spencer ha scritto:
> Thanks for the tip, Rob.
You're welcome, but I think we all have to thank Vlado Bartos, for this:
https://lists.gt.net/drbd/users/29049#29049
bye,
rob
___
drbd-user mailing list
drbd-user@lists.linbit.c
Thanks for the tip, Rob.
On 05/10/17 07:49, Roberto Resoli wrote:
Il 04/10/2017 12:37, Martyn Spencer ha scritto:
Hi Jay,
Thank you for your very detailed notes - they are very helpful. Out of
interest, is using cat /proc/drbd still useful with drbd 9? Would
watching drbdsetup status be the pr
Il 04/10/2017 12:37, Martyn Spencer ha scritto:
> Hi Jay,
>
> Thank you for your very detailed notes - they are very helpful. Out of
> interest, is using cat /proc/drbd still useful with drbd 9? Would
> watching drbdsetup status be the preferred equivalent now?
You can use this for "old-style" mo
personally I use drbdadm status, and the output seems the same,
The instructions I provided were from an older version of DRBD which I
have not fully updated yet
On 4 October 2017 at 11:37, Martyn Spencer
wrote:
> Hi Jay,
>
> Thank you for your very detailed notes - they are very helpful. Out of
Hi Jay,
Thank you for your very detailed notes - they are very helpful. Out of
interest, is using cat /proc/drbd still useful with drbd 9? Would
watching drbdsetup status be the preferred equivalent now?
Many thanks,
Martyn
On 03/10/17 10:02, Jason Fitzpatrick wrote:
Hi Martyn..
To fix co
oops, have to update my docs :)
On 4 October 2017 at 08:47, Robert Altnoeder
wrote:
> On 10/03/2017 11:02 AM, Jason Fitzpatrick wrote:
>> on one SSH session for each node run the following command
>>
>> watch cat /proc/drbd
>> this will allow you to monitor the status of the nodes as they attempt
On 10/03/2017 11:02 AM, Jason Fitzpatrick wrote:
> on one SSH session for each node run the following command
>
> watch cat /proc/drbd
> this will allow you to monitor the status of the nodes as they attempt
> to reconnect
There is no state information in this file in DRBD9 (only information
about
Hi Martyn..
To fix connectivity issues with DRBD
open up 2 ssh sessions to both nodes
on one SSH session for each node run the following command
watch cat /proc/drbd
this will allow you to monitor the status of the nodes as they attempt
to reconnect
on the node that states that it is secondary
Thank you for your assistance. Very helpful.
Regards,
Martyn
On 03/10/17 13:59, Robert Altnoeder wrote:
On 10/02/2017 12:37 PM, Martyn Spencer wrote:
I managed to put node1 into a state where it had pending actions that
I could not remove, so decided to remove the node and then re-add it.
Rat
On 10/02/2017 12:37 PM, Martyn Spencer wrote:
> I managed to put node1 into a state where it had pending actions that
> I could not remove, so decided to remove the node and then re-add it.
> Rather naively I did not check and the DRBD resources were all
> role:primary on node1. Now node1 is in a s
I am testing a three node DRBD 9.0.9 setup using packages I built for
CentOS7. I am using the latest drbdmanage and drbd-utils versions. If I
lose the data on the resources, it is fine (I am only testing) but I was
wanting to learn how to manage (if possible) the mess that I have just
caused :)
14 matches
Mail list logo
