OCF_HEARTBEAT_RAID1(7)

okay so bestie, you're on the OCF_HEARTBEAT_RAID1(7) page 💅 — this is all about ocf_heartbeat_Raid1, and we're gonna make Linux software RAID (MD) devices on shared storage make sense. no cap. ✨

🎀 NAME 🎀

ocf_heartbeat_Raid1 — manages Linux software RAID (MD) devices on shared storage 🦋

✨ SYNOPSIS ✨

Raid1 [start | stop | status | monitor | meta-data | validate-all]

🌸 DESCRIPTION 🌸

okay so this resource agent manages Linux software RAID (MD) devices on a shared storage medium. it uses mdadm(8) to start, stop, and monitor the MD devices. Raidtools are supported, but deprecated. see https://raid.wiki.kernel.org/index.php/Linux_Raid for more information. 💖

💜 SUPPORTED PARAMETERS 💜

• raidconf — the RAID configuration file, e.g. /etc/mdadm.conf. required, string, no default. 🎀
• raiddev — one or more block devices to use, space separated. alternatively, set it to "auto" to manage all devices specified in raidconf. required, string, no default. ✨
• homehost — the value for the homehost directive; this is an mdadm feature to protect RAIDs against being activated by accident. it is recommended to create RAIDs managed by the cluster with "homehost" set to a special value, so they are not accidentally auto-assembled by nodes not supposed to own them. optional, string, no default. 🦋
• force_stop — if processes or kernel threads are using the array, it cannot be stopped. the agent will try to stop processes, first by sending TERM and then, if that doesn't help in 3 seconds, using KILL. the lsof(8) program is required to get the list of array users. of course, the kernel threads cannot be stopped this way. if the processes are critical for data integrity, then set this parameter to false. note that in that case the stop operation will fail and the node will be fenced. optional, boolean, default true. 🚨
• udev — wait until udevd creates a device in the start operation. on a normally loaded host this should happen quickly, but you may be unlucky. if you are not using udev, set this to "no". optional, boolean, default true. ✨
• force_clones — activating the same md RAID array on multiple nodes at the same time will result in data corruption and thus is forbidden by default. a safe example could be an array that is only named identically across all nodes, but is in fact distinct. only set this to "true" if you know what you are doing! optional, boolean, default false. 💀

🔥 SUPPORTED ACTIONS 🔥

this resource agent supports the following actions (operations):

• start — starts the resource. suggested minimum timeout: 20s. 🌈
• stop — stops the resource. suggested minimum timeout: 20s. 🌈
• status — performs a status check. suggested minimum timeout: 20s. suggested interval: 10s. ⭐
• monitor — performs a detailed status check. suggested minimum timeout: 20s. suggested interval: 10s. ⭐
• validate-all — performs a validation of the resource configuration. suggested minimum timeout: 5s. 🧚
• meta-data — retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s. 🧚

🫶 EXAMPLE CRM SHELL 🫶

the following is an example configuration for a Raid1 resource using the crm(8) shell:

primitive p_Raid1 ocf:heartbeat:Raid1 \
  params \
    raidconf=string \
    raiddev=string \
  op monitor depth="0" timeout="20s" interval="10s"

💖 EXAMPLE PCS 💖

the following is an example configuration for a Raid1 resource using pcs(8)

pcs resource create p_Raid1 ocf:heartbeat:Raid1 \
  raidconf=string \
  raiddev=string \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s"

🦋 SEE ALSO 🦋

http://clusterlabs.org/

👑 AUTHOR 👑

ClusterLabs contributors (see the resource agent source for information about individual authors)

---

later, bestie! 🫶 this page comes from resource-agents, version UNKNOWN, dated 10/01/2026. slay. 💅