DRBD - Revision history

FilipeFonseca at 03:56, 1 November 2023

2023-11-01T03:56:44Z

← Older revision		Revision as of 03:56, 1 November 2023
Line 7:		Line 7:
	DRBD is part of the Lisog open source stack initiative.		DRBD is part of the Lisog open source stack initiative.

			=== DRBD usage ===
	DRBD usage

	- Maintenance:		- Maintenance:

Line 37:		Line 35:
	If all else fails and the machines are still in a split-brain condition then on the secondary (backup) machine issue:		If all else fails and the machines are still in a split-brain condition then on the secondary (backup) machine issue:
	drbdadm invalidate resource		drbdadm invalidate resource

			=== Resources cleanup ===
			With CRM:

			# crm resource cleanup <ALL(?)>

FilipeFonseca at 03:53, 1 November 2023

2023-11-01T03:53:06Z

← Older revision		Revision as of 03:53, 1 November 2023
Line 21:		Line 21:

	--reboot.done.		--reboot.done.

			=== SPLIT-BRAIN resolve ===
			After split brain has been detected, one node will always have the resource in a '''StandAlone''' connection state. The other might either also be in the '''StandAlone''' state (if both nodes detected the split brain simultaneously), or in '''WFConnection''' (if the peer tore down the connection before the other node had a chance to detect split brain).

			At this point, unless you configured DRBD to automatically recover from split brain, you must manually intervene by selecting one node whose modifications will be discarded (this node is referred to as the split brain victim). This intervention is made with the following commands:
			# drbdadm secondary resource

			# drbdadm disconnect resource

			# drbdadm -- --discard-my-data connect resource
			On the other node (the split brain survivor), if its connection state is also StandAlone, you would enter:
			# drbdadm connect resource
			You may omit this step if the node is already in the WFConnection state; it will then reconnect automatically.

			If all else fails and the machines are still in a split-brain condition then on the secondary (backup) machine issue:
			drbdadm invalidate resource

FilipeFonseca at 18:31, 7 February 2022

2022-02-07T18:31:50Z

← Older revision		Revision as of 18:31, 7 February 2022
Line 21:		Line 21:

	--reboot.done.		--reboot.done.

	~~- Transfer role:~~

	~~--CRM# resource move iSCSI_group1 inode02ss force~~

FilipeFonseca at 18:23, 7 February 2022

2022-02-07T18:23:30Z

← Older revision		Revision as of 18:23, 7 February 2022
Line 1:		Line 1:
	DRBD		'''DRBD''' is a distributed replicated storage system for the Linux platform. It is implemented as a kernel driver, several userspace management applications, and some shell scripts. DRBD is traditionally used in high availability (HA) computer clusters, but beginning with DRBD version 9, it can also be used to create larger software defined storage pools with a focus on cloud integration.

			A ''DRBD device'' is a ''DRBD block device'' that refers to a logical block device in a logical volume schema.

			The DRBD software is free software released under the terms of the GNU General Public License version 2.

			DRBD is part of the Lisog open source stack initiative.


			DRBD usage

	- Maintenance:		- Maintenance:

FilipeFonseca: Created page with "DRBD - Maintenance: --drbdadm status #get node array status --cat /proc/drbd #check connection and role --drbdadmin disconnect <…name…> #disconnect array ..."

2022-02-07T18:21:12Z

Created page with "DRBD - Maintenance: --drbdadm status #get node array status --cat /proc/drbd #check connection and role --drbdadmin disconnect <…name…> #disconnect array <tasks...>..."

New page

DRBD

- Maintenance:

--drbdadm status #get node array status

--cat /proc/drbd #check connection and role

--drbdadmin disconnect <…name…> #disconnect array

<tasks...>

--reboot.done.

- Transfer role:

--CRM# resource move iSCSI_group1 inode02ss force