OCF_HEARTBEAT_ZFS(7)
π OCF_HEARTBEAT_ZFS π
okay bestie, welcome to ocf_heartbeat_ZFS β that's the OCF_HEARTBEAT_ZFS(7) manual page, and she's literally the resource agent that manages ZFS pools. no cap. let's get into it π¦
β¨ NAME β¨
ocf_heartbeat_ZFS β manages ZFS pools. that's it, that's the whole job, and she does it flawlessly π
πΈ SYNOPSIS πΈ
ZFS [start | stop | monitor | meta-data | validate-all]
five actions, pick your fighter π
π DESCRIPTION π
so this script manages ZFS pools π«Ά it can import a ZFS pool, or export it. import = she's in her welcoming era, bringing the pool into the picture. export = she's saying bye, gracefully, main character exit. that's the vibe. that's the whole thing. it's giving "I do one job and I ate." π₯
π SUPPORTED PARAMETERS π
these are the lil knobs you get to turn, bestie. read them carefully, fr fr:
poolβ the name of the ZFS pool she's gonna manage, like"tank". for example:"tank". that's the example, that's the pool name. (unique, required, string, no default) β so yeah, you HAVE to give her one, there's no backup plan here πimportargsβ the arguments handed over tozpool import, e.g."-d /dev/disk/by-id". (optional, string, no default) β optional, so if you don't say anything, nothing gets passed. she respects your silence β¨importforceβ when this is on,zpool importgets handed the-foption. (optional, boolean, default true) β lowkey important: the default is true, so out of the box she IS force-importing. if you don't want the-f, you gotta say so yourself π
π SUPPORTED ACTIONS π
this resource agent supports the following actions (operations) β and each one comes with a suggested minimum timeout, which is basically the "girl, give me at least this long" number:
startβ starts the resource. suggested minimum timeout: 60s. βstopβ stops the resource. suggested minimum timeout: 60s. πmonitorβ performs a detailed status check. suggested minimum timeout: 30s. suggested interval: 5s. she's checking in on you every 5 seconds, that's love π₯Ίvalidate-allβ performs a validation of the resource configuration. suggested minimum timeout: 30s. π§meta-dataβ retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s. not for you, bestie, that's her private business π
π EXAMPLE CRM SHELL π
here's what a ZFS resource config looks like using the crm(8) shell. copy-paste-able, iconic, no notes:
primitive p_ZFS ocf:heartbeat:ZFS \
params \
pool=string \
op monitor depth="0" timeout="30s" interval="5s"
π EXAMPLE PCS π
and here's the same energy for a ZFS resource using pcs(8) β different tool, same slay:
pcs resource create p_ZFS ocf:heartbeat:ZFS \
pool=string \
op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="5s"
π SEE ALSO π
http://clusterlabs.org/β go say hi, she's lovely π
π«Ά AUTHOR π«Ά
ClusterLabs contributors (see the resource agent source for information about individual authors). a whole squad of legends, and honestly? we stan πΈ
ok that's the whole page bestie, you're officially ZFS-pilled. go forth and manage those pools π β¨
and that's a wrap!! this was resource-agents UNKNOWN, dated 04/08/2026 β written from the OCF_HEARTBEAT_ZFS(7) manual page. mwah, bye bye ππ
π¦ where this page comes from
- fedora 43: resource-agents 4.18.0-1.fc43 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- fedora 44: resource-agents 4.18.0-1.fc44 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms