]> git.ipfire.org Git - thirdparty/systemd.git/blame - man/systemd.mount.xml
man: mention that x-systemd.device-timeout is only for fstab
[thirdparty/systemd.git] / man / systemd.mount.xml
CommitLineData
cdb788e4
LP
1<?xml version='1.0'?> <!--*-nxml-*-->
2<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
3<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
4 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
5
6<!--
7 This file is part of systemd.
8
9 Copyright 2010 Lennart Poettering
10
11 systemd is free software; you can redistribute it and/or modify it
5430f7f2
LP
12 under the terms of the GNU Lesser General Public License as published by
13 the Free Software Foundation; either version 2.1 of the License, or
cdb788e4
LP
14 (at your option) any later version.
15
16 systemd is distributed in the hope that it will be useful, but
17 WITHOUT ANY WARRANTY; without even the implied warranty of
18 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
5430f7f2 19 Lesser General Public License for more details.
cdb788e4 20
5430f7f2 21 You should have received a copy of the GNU Lesser General Public License
cdb788e4
LP
22 along with systemd; If not, see <http://www.gnu.org/licenses/>.
23-->
24
25<refentry id="systemd.mount">
26 <refentryinfo>
27 <title>systemd.mount</title>
28 <productname>systemd</productname>
29
30 <authorgroup>
31 <author>
32 <contrib>Developer</contrib>
33 <firstname>Lennart</firstname>
34 <surname>Poettering</surname>
35 <email>lennart@poettering.net</email>
36 </author>
37 </authorgroup>
38 </refentryinfo>
39
40 <refmeta>
41 <refentrytitle>systemd.mount</refentrytitle>
42 <manvolnum>5</manvolnum>
43 </refmeta>
44
45 <refnamediv>
46 <refname>systemd.mount</refname>
34511ca7 47 <refpurpose>Mount unit configuration</refpurpose>
cdb788e4
LP
48 </refnamediv>
49
50 <refsynopsisdiv>
e670b166 51 <para><filename><replaceable>mount</replaceable>.mount</filename></para>
cdb788e4
LP
52 </refsynopsisdiv>
53
54 <refsect1>
55 <title>Description</title>
56
57 <para>A unit configuration file whose name ends in
479fe882 58 <literal>.mount</literal> encodes information about
65232ea7
LP
59 a file system mount point controlled and supervised by
60 systemd.</para>
cdb788e4
LP
61
62 <para>This man page lists the configuration options
63 specific to this unit type. See
64 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
65 for the common options of all unit configuration
66 files. The common configuration items are configured
67 in the generic [Unit] and [Install] sections. The
68 mount specific configuration options are configured
69 in the [Mount] section.</para>
70
71 <para>Additional options are listed in
ba60f905
LP
72 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
73 which define the execution environment the
74 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
4819ff03 75 binary is executed in, and in
d868475a
ZJS
76 <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
77 which define the way the processes are terminated, and
78 in
3fde5f30
LP
79 <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
80 which configure resource control settings for the
d868475a
ZJS
81 processes of the service. Note that the User= and
82 Group= options are not particularly useful for mount
83 units specifying a <literal>Type=</literal> option or
84 using configuration not specified in
85 <filename>/etc/fstab</filename>;
8a117511 86 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
6b4991cf 87 will refuse options that are not listed in
8a117511
LP
88 <filename>/etc/fstab</filename> if it is not run as
89 UID 0.</para>
cdb788e4 90
e0cabd4b
LP
91 <para>Mount units must be named after the mount point
92 directories they control. Example: the mount point
845c5324 93 <filename noindex='true'>/home/lennart</filename> must be configured
cdb788e4
LP
94 in a unit file
95 <filename>home-lennart.mount</filename>. For details
96 about the escaping logic used to convert a file system
b040723e 97 path to a unit name, see
cdb788e4 98 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
65232ea7
LP
99
100 <para>Optionally, a mount unit may be accompanied by
101 an automount unit, to allow on-demand or parallelized
102 mounting. See
103 <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
e0cabd4b 104
f848f8d8 105 <para>If a mount point is beneath another mount point
b439c6ee 106 in the file system hierarchy, a dependency between both
e0cabd4b 107 units is created automatically.</para>
b36b082c 108
236bc757
LP
109 <para>Mount points created at runtime (independently of
110 unit files or <filename>/etc/fstab</filename>) will be
b36b082c 111 monitored by systemd and appear like any other mount
e22ac43b
ZJS
112 unit in systemd.
113 See <filename>/proc/self/mountinfo</filename> description
114 in <citerefentry><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
115 </para>
236bc757
LP
116
117 <para>Some file systems have special semantics as API
118 file systems for kernel-to-userspace and
119 userspace-to-userpace interfaces. Some of them may not
120 be changed via mount units, and cannot be disabled.
121 For a longer discussion see <ulink
122 url="http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems">API
123 File Systems</ulink>.</para>
cdb788e4
LP
124 </refsect1>
125
126 <refsect1>
fa4ab997 127 <title><filename>/etc/fstab</filename></title>
cdb788e4
LP
128
129 <para>Mount units may either be configured via unit
130 files, or via <filename>/etc/fstab</filename> (see
131 <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>
059b37cc
LP
132 for details). Mounts listed in
133 <filename>/etc/fstab</filename> will be converted into
134 native units dynamically at boot and when the
72ebbf34
ZJS
135 configuration of the system manager is reloaded. In
136 general, configuring mount points through
137 <filename>/etc/fstab</filename> is the preferred
138 approach. See
059b37cc
LP
139 <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
140 for details about the conversion.</para>
cdb788e4
LP
141
142 <para>When reading <filename>/etc/fstab</filename> a
143 few special mount options are understood by systemd
144 which influence how dependencies are created for mount
92a39ae1
LP
145 points from <filename>/etc/fstab</filename>. systemd
146 will create a dependency of type
63b03c0b
ZJS
147 <option>Wants</option> or <option>Requires</option>
148 (see option <option>nofail</option> below), from
149 either <filename>local-fs.target</filename> or
cdb788e4 150 <filename>remote-fs.target</filename>, depending
63b03c0b
ZJS
151 whether the file system is local or remote.</para>
152
153 <variablelist class='fstab-options'>
154
155 <varlistentry>
156 <term><option>x-systemd.automount</option></term>
157
158 <listitem><para>An automount unit will be created
159 for the file system. See
160 <citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
161 for details.</para></listitem>
162 </varlistentry>
163
164 <varlistentry>
165 <term><option>x-systemd.device-timeout=</option></term>
166
167 <listitem><para>Configure how long systemd should
168 wait for a device to show up before giving up on
169 an entry from
170 <filename>/etc/fstab</filename>. Specify a time in
171 seconds or explicitly append a unit as
172 <literal>s</literal>, <literal>min</literal>,
173 <literal>h</literal>,
174 <literal>ms</literal>.</para>
175
176 <para>Note that this option can only be used in
177 <filename>/etc/fstab</filename>, and will be
178 ignored when part of <varname>Options=</varname>
179 setting in a unit file.</para>
180 </listitem>
181 </varlistentry>
182
183 <varlistentry>
184 <term><option>nofail</option></term>
185 <term><option>fail</option></term>
186
187 <listitem><para>With <option>nofail</option> this
188 mount will be only wanted, not required, by the
189 <filename>local-fs.target</filename>. This means
190 that the boot will continue even if this mount
191 point is not mounted successfully. Option
192 <option>fail</option> has the opposite meaning and
193 is the default.</para>
194 </listitem>
195 </varlistentry>
196
197 <varlistentry>
198 <term><option>noauto</option></term>
199 <term><option>auto</option></term>
200
201 <listitem><para>With <option>noauto</option>, this
202 mount will not be added as a dependency for
203 <filename>local-fs.target</filename>. This means
204 that it will not be mounted automatically during
205 boot, unless it is pulled in by some other
206 unit. Option <option>auto</option> has the
207 opposite meaning and is the default.</para>
208 </listitem>
209 </varlistentry>
210 </variablelist>
72ebbf34 211
cdb788e4 212 <para>If a mount point is configured in both
c32247e9 213 <filename>/etc/fstab</filename> and a unit file that
79640424 214 is stored below <filename>/usr</filename>, the former
c32247e9 215 will take precedence. If the unit file is stored below
79640424 216 <filename>/etc</filename>, it will take
c32247e9
LP
217 precedence. This means: native unit files take
218 precedence over traditional configuration files, but
219 this is superseded by the rule that configuration in
220 <filename>/etc</filename> will always take precedence
221 over configuration in
222 <filename>/usr</filename>.</para>
cdb788e4
LP
223 </refsect1>
224
225 <refsect1>
226 <title>Options</title>
227
228 <para>Mount files must include a [Mount] section,
229 which carries information about the file system mount points it
230 supervises. A number of options that may be used in
231 this section are shared with other unit types. These
232 options are documented in
4819ff03
LP
233 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
234 and
235 <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>. The
65232ea7 236 options specific to the [Mount] section of mount
cdb788e4
LP
237 units are the following:</para>
238
ccc9a4f9 239 <variablelist class='unit-directives'>
cdb788e4
LP
240
241 <varlistentry>
242 <term><varname>What=</varname></term>
243 <listitem><para>Takes an absolute path
244 of a device node, file or other
245 resource to mount. See
246 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
247 for details. If this refers to a
b439c6ee 248 device node, a dependency on the
cdb788e4
LP
249 respective device unit is
250 automatically created. (See
251 <citerefentry><refentrytitle>systemd.device</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more information.)
252 This option is
253 mandatory.</para></listitem>
254 </varlistentry>
255
256 <varlistentry>
257 <term><varname>Where=</varname></term>
258 <listitem><para>Takes an absolute path
259 of a directory of the mount point. If
f848f8d8 260 the mount point does not exist at the
b439c6ee 261 time of mounting, it is created. This
cdb788e4 262 string must be reflected in the unit
e9dd9f95 263 filename. (See above.) This option is
cdb788e4
LP
264 mandatory.</para></listitem>
265 </varlistentry>
266
267 <varlistentry>
268 <term><varname>Type=</varname></term>
269 <listitem><para>Takes a string for the
e9dd9f95 270 file system type. See
cdb788e4
LP
271 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>
272 for details. This setting is
273 optional.</para></listitem>
274 </varlistentry>
275
276 <varlistentry>
277 <term><varname>Options=</varname></term>
278
279 <listitem><para>Mount options to use
e9dd9f95
JSJ
280 when mounting. This takes a
281 comma-separated list of options. This
cdb788e4
LP
282 setting is optional.</para></listitem>
283 </varlistentry>
284
285 <varlistentry>
2dbd4a94
LP
286 <term><varname>SloppyOptions=</varname></term>
287
288 <listitem><para>Takes a boolean
8d0e0ddd 289 argument. If true, parsing of the
2dbd4a94
LP
290 options specified in
291 <varname>Options=</varname> is
292 relaxed, and unknown mount options are
293 tolerated. This corresponds with
294 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s
295 <parameter>-s</parameter>
296 switch. Defaults to
297 off.</para></listitem>
298 </varlistentry>
299
300 <varlistentry>
cdb788e4
LP
301 <term><varname>DirectoryMode=</varname></term>
302 <listitem><para>Directories of mount
303 points (and any parent directories)
304 are automatically created if
305 needed. This option specifies the file
306 system access mode used when creating
dd1eb43b
LP
307 these directories. Takes an access
308 mode in octal notation. Defaults to
cdb788e4
LP
309 0755.</para></listitem>
310 </varlistentry>
311
312 <varlistentry>
313 <term><varname>TimeoutSec=</varname></term>
314 <listitem><para>Configures the time to
315 wait for the mount command to
b439c6ee 316 finish. If a command does not exit
e9dd9f95 317 within the configured time, the mount
cdb788e4
LP
318 will be considered failed and be shut
319 down again. All commands still running
320 will be terminated forcibly via
05cc7267
ZJS
321 <constant>SIGTERM</constant>, and after another delay of
322 this time with <constant>SIGKILL</constant>. (See
4819ff03
LP
323 <option>KillMode=</option> in
324 <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.)
cdb788e4
LP
325 Takes a unit-less value in seconds, or
326 a time span value such as "5min
327 20s". Pass 0 to disable the timeout
63ba209d
JE
328 logic. The default value is set from the manager configuration
329 file's <varname>DefaultTimeoutStart=</varname> variable.</para></listitem>
cdb788e4 330 </varlistentry>
c485d3ba 331 </variablelist>
4819ff03
LP
332
333 <para>Check
334 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
335 and
336 <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>
337 for more settings.</para>
c485d3ba
LP
338 </refsect1>
339
cdb788e4
LP
340 <refsect1>
341 <title>See Also</title>
342 <para>
f3e219a2 343 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
cdb788e4
LP
344 <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
345 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
346 <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
4819ff03 347 <citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
3fde5f30 348 <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
66b1a247 349 <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
cdb788e4 350 <citerefentry><refentrytitle>systemd.device</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
e22ac43b 351 <citerefentry><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
059b37cc 352 <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
9cc2c8b7
ZJS
353 <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
354 <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
cdb788e4
LP
355 </para>
356 </refsect1>
357
358</refentry>