My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

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 12
SUSE Linux Enterprise High Availability Extension 11 Service Pack 4

Situation

At times you need to change the default values of the SBD partition or even recreate it on a different device.  This can be done while the cluster and resources are up and running following these steps.

Resolution

Note: If you are concerned while doing this you can put the cluster in maintenance mode during this so that the cluster does not react to any failures.
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

When using the SLES11 method on SLES12, the sbd processes would not stop properly if you needed to stop pacemaker service for any reason. 

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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-16
  • Modified Date:22-FEB-17
    • SUSESUSE Linux Enterprise High Availability Extension
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center