1OCF_HEARTBEAT_FILESY(7) OCF resource agents OCF_HEARTBEAT_FILESY(7)
2
6 ocf_heartbeat_Filesystem - Manages filesystem mounts
7
9 Filesystem [start | stop | monitor | meta-data | validate-all]
10
12 Resource script for Filesystem. It manages a Filesystem on a shared
13 storage medium.
14 The standard monitor operation of depth 0 (also known as probe) checks
16 if the filesystem is mounted. If you want deeper tests, set
17 OCF_CHECK_LEVEL to one of the following values:
18 10: read first 16 blocks of the device (raw read)
20 This doesn't exercise the filesystem at all, but the device on which
22 the filesystem lives. This is noop for non-block devices such as NFS,
23 SMBFS, or bind mounts.
24 20: test if a status file can be written and read
26 The status file must be writable by root. This is not always the case
28 with an NFS mount, as NFS exports usually have the "root_squash" option
29 set. In such a setup, you must either use read-only monitoring
30 (depth=10), export with "no_root_squash" on your NFS server, or grant
31 world write permissions on the directory where the status file is to be
32 placed.
33
35 device
36 The name of block device for the filesystem, or -U, -L options for
37 mount, or NFS mount specification. (required, string, no default)
38 directory
40 The mount point for the filesystem. (required, string, no default)
41 fstype
43 The type of filesystem to be mounted. (required, string, no
44 default)
45 options
47 Any extra options to be given as -o options to mount. .sp For bind
48 mounts, add "bind" here and set fstype to "none". We will do the
49 right thing for options such as "bind,ro". (optional, string, no
50 default)
51 statusfile_prefix
53 The prefix to be used for a status file for resource monitoring
54 with depth 20. If you don't specify this parameter, all status
55 files will be created in a separate directory. (optional, string,
56 default .Filesystem_status/)
57 run_fsck
59 Specify how to decide whether to run fsck or not. .sp "auto" :
60 decide to run fsck depending on the fstype(default) "force" :
61 always run fsck regardless of the fstype "no" : do not run fsck
62 ever. (optional, string, default auto)
63 fast_stop
65 Normally, we expect no users of the filesystem and the stop
66 operation to finish quickly. If you cannot control the filesystem
67 users easily and want to prevent the stop action from failing, then
68 set this parameter to "no" and add an appropriate timeout for the
69 stop operation. (optional, boolean, default yes)
70
72 This resource agent supports the following actions (operations):
73 start
75 Starts the resource. Suggested minimum timeout: 60.
76 stop
78 Stops the resource. Suggested minimum timeout: 60.
79 notify
81 Suggested minimum timeout: 60.
82 monitor
84 Performs a detailed status check. Suggested minimum timeout: 40.
85 Suggested interval: 20.
86 validate-all
88 Performs a validation of the resource configuration. Suggested
89 minimum timeout: 5.
90 meta-data
92 Retrieves resource agent metadata (internal use only). Suggested
93 minimum timeout: 5.
94
96 The following is an example configuration for a Filesystem resource
97 using the crm(8) shell:
98 primitive p_Filesystem ocf:heartbeat:Filesystem \
100 params \
101 device=string \
102 directory=string \
103 fstype=string \
104 op monitor depth="0" timeout="40" interval="20"
105
107 http://www.linux-ha.org/wiki/Filesystem_(resource_agent)
108
110 Linux-HA contributors (see the resource agent source for information
111 about individual authors)
112resource-agents 3.9.2 07/08/2011 OCF_HEARTBEAT_FILESY(7)