How to recreate SBD partition in a SUSE HA cluster.
This document (7018194) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 11 Service Pack 4
Situation
Resolution
Example: crm configure property maintenance-mode=true
SLES11 steps:
1. Stop the stonith sbd primitive in the cluster.
2. Check the /etc/sysconfig/sbd configuration file to see which device and options are currently used.
Example:
SBD_DEVICE="/dev/sdb1"
SBD_OPTS="-W -P"
3. Stop sbd on all nodes and all devices: sbd –d <device> message LOCAL exit
Verify that the sbd processes are no longer running. These processes will be gone after running the command.
ps -eaf | grep sbd
root 8695 1 0 13:11 pts/0 00:00:00 sbd: inquisitor
root 8696 8695 0 13:11 pts/0 00:00:00 sbd: watcher: /dev/sdb1 - slot: 0 - uuid: 47c245cb-2c80-49b5-9d1d-c2ec246c2f0a
root 8699 8695 0 13:11 pts/0 00:00:01 sbd: watcher: Pacemaker
4. Create the new sbd partition/s on one of the nodes. Make sure you use same device that's in /etc/sysconfig/sbd
Example: sbd -d /dev/sdb1 -1 30 -4 60 create
Note: If the device is different than before, you will need to update the /etc/sysconfig/sbd on each node with the new device.
5. Restart the sbd processes with the options defined in the /etc/sysconfig/sbd on all nodes in the cluster.
sbd –d <device> watch -P
Verify that the same processes were restarted as we saw in step 3.
6. Start the stonith primitive in the cluster.
SLES12 steps (different because of systemd)
1. Stop the stonith sbd primitive in the cluster.
2. Check the /etc/sysconfig/sbd configuration file to see which device and options are currently used.
Example:
SBD_DEVICE="/dev/sdb1"
SBD_OPTS="-W -P"
3. Stop sbd on all nodes and all devices: Use the following script: /usr/share/sbd/sbd.sh stop
Verify that the sbd processes are no longer running. These processes will be gone after running the command.
ps -eaf | grep sbd
root 8695 1 0 13:11 pts/0 00:00:00 sbd: inquisitor
root 8696 8695 0 13:11 pts/0 00:00:00 sbd: watcher: /dev/sdb1 - slot: 0 - uuid: 47c245cb-2c80-49b5-9d1d-c2ec246c2f0a
root 8699 8695 0 13:11 pts/0 00:00:01 sbd: watcher: Pacemaker
4. Create the new sbd partition/s on one of the nodes. Make sure you use same device that's in /etc/sysconfig/sbd
Example: sbd -d /dev/sdb1 -1 30 -4 60 create
Note: If the device is different than before, you will need to update the /etc/sysconfig/sbd on each node with the new device.
5. At this point, just start the pacemaker service again on each node. Example: systemctl start pacemaker
This will run the "sbd.sh start" but properly link it in systemd and you will not have any issues when stopping pacemaker
Verify that the same processes were restarted as we saw in step 3.
6. Start the stonith primitive in the cluster.
Note: if you put cluster in maintenance mode, you can now take it out of maintenance mode.
Example: crm configure property maintenance-mode=false
Cause
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7018194
- Creation Date: 26-Oct-2016
- Modified Date:03-Mar-2020
-
- SUSE Linux Enterprise High Availability Extension
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com