Debian Codegraph @

upstream/debian-unstable/man5/systemd.mount.5

raw
1 '\" t
2 .TH "SYSTEMD\&.MOUNT" "5" "" "systemd 261~rc3" "systemd.mount"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd.mount \- Mount unit configuration
24 .SH "SYNOPSIS"
25 .PP
26 \fImount\fR\&.mount
27 .SH "DESCRIPTION"
28 .PP
29 A unit configuration file whose name ends in
30 "\&.mount"
31 encodes information about a file system mount point controlled and supervised by systemd\&.
32 .PP
33 This man page lists the configuration options specific to this unit type\&. See
34 \fBsystemd.unit\fR(5)
35 for the common options of all unit configuration files\&. The common configuration items are configured in the generic [Unit] and [Install] sections\&. The mount specific configuration options are configured in the [Mount] section\&.
36 .PP
37 Additional options are listed in
38 \fBsystemd.exec\fR(5), which define the execution environment the
39 \fBmount\fR(8)
40 program is executed in, and in
41 \fBsystemd.kill\fR(5), which define the way the processes are terminated, and in
42 \fBsystemd.resource-control\fR(5), which configure resource control settings for the processes of the service\&.
43 .PP
44 Note that the options
45 \fIUser=\fR
46 and
47 \fIGroup=\fR
48 are not useful for mount units\&. systemd passes two parameters to
49 \fBmount\fR(8); the values of
50 \fIWhat=\fR
51 and
52 \fIWhere=\fR\&. When invoked in this way,
53 \fBmount\fR(8)
54 does not read any options from
55 /etc/fstab, and must be run as UID 0\&.
56 .PP
57 Mount units must be named after the mount point directories they control\&. Example: the mount point
58 /home/lennart
59 must be configured in a unit file
60 home\-lennart\&.mount\&. For details about the escaping logic used to convert a file system path to a unit name, see
61 \fBsystemd.unit\fR(5)\&. Note that mount units cannot be templated, nor is possible to add multiple names to a mount unit by creating symlinks to its unit file\&.
62 .PP
63 Optionally, a mount unit may be accompanied by an automount unit, to allow on\-demand or parallelized mounting\&. See
64 \fBsystemd.automount\fR(5)\&.
65 .PP
66 Mount points created at runtime (independently of unit files or
67 /etc/fstab) will be monitored by systemd and appear like any other mount unit in systemd\&. See
68 /proc/self/mountinfo
69 description in
70 \fBproc\fR(5)\&.
71 .PP
72 Some file systems have special semantics as API file systems for kernel\-to\-userspace and userspace\-to\-userspace interfaces\&. Some of them may not be changed via mount units, and cannot be disabled\&. For a longer discussion see
73 \m[blue]\fBAPI File Systems\fR\m[]\&\s-2\u[1]\d\s+2\&.
74 .PP
75 The
76 \fBsystemd-mount\fR(1)
77 command allows creating
78 \&.mount
79 and
80 \&.automount
81 units dynamically and transiently from the command line\&.
82 .SH "AUTOMATIC DEPENDENCIES"
83 .SS "Implicit Dependencies"
84 .PP
85 The following dependencies are implicitly added:
86 .sp
87 .RS 4
88 .ie n \{\
89 \h'-04'\(bu\h'+03'\c
90 .\}
91 .el \{\
92 .sp -1
93 .IP \(bu 2.3
94 .\}
95 If a mount unit is beneath another mount unit in the file system hierarchy, both a requirement dependency and an ordering dependency between both units are created automatically\&.
96 .RE
97 .sp
98 .RS 4
99 .ie n \{\
100 \h'-04'\(bu\h'+03'\c
101 .\}
102 .el \{\
103 .sp -1
104 .IP \(bu 2.3
105 .\}
106 Block device backed file systems automatically gain
107 \fIRequires=\fR,
108 \fIStopPropagatedFrom=\fR, and
109 \fIAfter=\fR
110 type dependencies on the device unit encapsulating the block device (see
111 \fIx\-systemd\&.device\-bound=\fR
112 for details)\&.
113 .RE
114 .sp
115 .RS 4
116 .ie n \{\
117 \h'-04'\(bu\h'+03'\c
118 .\}
119 .el \{\
120 .sp -1
121 .IP \(bu 2.3
122 .\}
123 If traditional file system quota is enabled for a mount unit, automatic
124 \fIWants=\fR
125 and
126 \fIBefore=\fR
127 dependencies on
128 systemd\-quotacheck@\&.service
129 and
130 quotaon@\&.service
131 are added\&.
132 .RE
133 .sp
134 .RS 4
135 .ie n \{\
136 \h'-04'\(bu\h'+03'\c
137 .\}
138 .el \{\
139 .sp -1
140 .IP \(bu 2.3
141 .\}
142 Additional implicit dependencies may be added as result of execution and resource control parameters as documented in
143 \fBsystemd.exec\fR(5)
144 and
145 \fBsystemd.resource-control\fR(5)\&.
146 .RE
147 .SS "Default Dependencies"
148 .PP
149 The following dependencies are added unless
150 \fIDefaultDependencies=no\fR
151 is set:
152 .sp
153 .RS 4
154 .ie n \{\
155 \h'-04'\(bu\h'+03'\c
156 .\}
157 .el \{\
158 .sp -1
159 .IP \(bu 2.3
160 .\}
161 All mount units acquire automatic
162 \fIBefore=\fR
163 and
164 \fIConflicts=\fR
165 on
166 umount\&.target
167 in order to be stopped during shutdown\&.
168 .RE
169 .sp
170 .RS 4
171 .ie n \{\
172 \h'-04'\(bu\h'+03'\c
173 .\}
174 .el \{\
175 .sp -1
176 .IP \(bu 2.3
177 .\}
178 Mount units referring to local file systems automatically gain an
179 \fIAfter=\fR
180 dependency on
181 local\-fs\-pre\&.target, and a
182 \fIBefore=\fR
183 dependency on
184 local\-fs\&.target
185 unless one or more mount options among
186 \fBnofail\fR,
187 \fBx\-systemd\&.wanted\-by=\fR, and
188 \fBx\-systemd\&.required\-by=\fR
189 is set\&. See below for detailed information\&.
190 .sp
191 Additionally, an
192 \fIAfter=\fR
193 dependency on
194 swap\&.target
195 is added when the file system type is
196 "tmpfs"\&.
197 .RE
198 .sp
199 .RS 4
200 .ie n \{\
201 \h'-04'\(bu\h'+03'\c
202 .\}
203 .el \{\
204 .sp -1
205 .IP \(bu 2.3
206 .\}
207 Network mount units automatically acquire
208 \fIAfter=\fR
209 dependencies on
210 remote\-fs\-pre\&.target,
211 network\&.target, plus
212 \fIAfter=\fR
213 and
214 \fIWants=\fR
215 dependencies on
216 network\-online\&.target, and a
217 \fIBefore=\fR
218 dependency on
219 remote\-fs\&.target, unless one or more mount options among
220 \fBnofail\fR,
221 \fBx\-systemd\&.wanted\-by=\fR, and
222 \fBx\-systemd\&.required\-by=\fR
223 is set\&.
224 .RE
225 .PP
226 Mount units referring to local and network file systems are distinguished by their file system type specification\&. In some cases this is not sufficient (for example network block device based mounts, such as iSCSI), in which case
227 \fB_netdev\fR
228 may be added to the mount option string of the unit, which forces systemd to consider the mount unit a network mount\&.
229 .SH "FSTAB"
230 .PP
231 Mount units may either be configured via unit files, or via
232 /etc/fstab
233 (see
234 \fBfstab\fR(5)
235 for details)\&. Mounts listed in
236 /etc/fstab
237 will be converted into native units dynamically at boot and when the configuration of the system manager is reloaded\&. In general, configuring mount points through
238 /etc/fstab
239 is the preferred approach to manage mounts for humans\&. For tooling, writing mount units should be preferred over editing
240 /etc/fstab\&. See
241 \fBsystemd-fstab-generator\fR(8)
242 for details about the conversion from
243 /etc/fstab
244 to mount units\&.
245 .PP
246 The NFS mount option
247 \fBbg\fR
248 for NFS background mounts as documented in
249 \fBnfs\fR(5)
250 is detected by
251 \fBsystemd\-fstab\-generator\fR
252 and the options are transformed so that systemd fulfills the job\-control implications of that option\&. Specifically
253 \fBsystemd\-fstab\-generator\fR
254 acts as though
255 "x\-systemd\&.mount\-timeout=infinity,retry=10000"
256 was prepended to the option list, and
257 "fg,nofail"
258 was appended\&. Depending on specific requirements, it may be appropriate to provide some of these options explicitly, or to make use of the
259 "x\-systemd\&.automount"
260 option described below instead of using
261 "bg"\&.
262 .PP
263 When reading
264 /etc/fstab
265 a few special mount options are understood by systemd which influence how dependencies are created for mount points\&. systemd will create a dependency of type
266 \fIWants=\fR
267 or
268 \fBRequires=\fR
269 (see option
270 \fBnofail\fR
271 below), from either
272 local\-fs\&.target
273 or
274 remote\-fs\&.target, depending whether the file system is local or remote\&.
275 .PP
276 \fBx\-systemd\&.requires=\fR
277 .RS 4
278 Configures a
279 \fIRequires=\fR
280 and an
281 \fIAfter=\fR
282 dependency between the created mount unit and another systemd unit, such as a device or mount unit\&. The argument should be a unit name, or an absolute path to a device node or mount point\&. This option may be specified more than once\&. This option is particularly useful for mount point declarations that need an additional device to be around (such as an external journal device for journal file systems) or an additional mount to be in place (such as an overlay file system that merges multiple mount points)\&. See
283 \fIAfter=\fR
284 and
285 \fIRequires=\fR
286 in
287 \fBsystemd.unit\fR(5)
288 for details\&.
289 .sp
290 Note that this option always applies to the created mount unit only regardless whether
291 \fBx\-systemd\&.automount\fR
292 has been specified\&.
293 .sp
294 Added in version 220\&.
295 .RE
296 .PP
297 \fBx\-systemd\&.wants=\fR
298 .RS 4
299 Configures a
300 \fIWants=\fR
301 and an
302 \fIAfter=\fR
303 dependency between the created mount unit and another systemd unit, similar to the
304 \fIx\-systemd\&.requires=\fR
305 option\&.
306 .sp
307 Added in version 257\&.
308 .RE
309 .PP
310 \fBx\-systemd\&.before=\fR, \fBx\-systemd\&.after=\fR
311 .RS 4
312 In the created mount unit, configures a
313 \fIBefore=\fR
314 or
315 \fIAfter=\fR
316 dependency on another systemd unit, such as a mount unit\&. The argument should be a unit name or an absolute path to a mount point\&. This option may be specified more than once\&. This option is particularly useful for mount point declarations with
317 \fBnofail\fR
318 option that are mounted asynchronously but need to be mounted before or after some unit start, for example, before
319 local\-fs\&.target
320 unit\&. See
321 \fIBefore=\fR
322 and
323 \fIAfter=\fR
324 in
325 \fBsystemd.unit\fR(5)
326 for details\&.
327 .sp
328 Note that these options always apply to the created mount unit only regardless whether
329 \fBx\-systemd\&.automount\fR
330 has been specified\&.
331 .sp
332 Added in version 233\&.
333 .RE
334 .PP
335 \fBx\-systemd\&.wanted\-by=\fR, \fBx\-systemd\&.required\-by=\fR
336 .RS 4
337 In the created mount unit, configures a
338 \fIWantedBy=\fR
339 or
340 \fIRequiredBy=\fR
341 dependency on another unit\&. This option may be specified more than once\&. If this is specified, the default dependencies (see above) other than
342 umount\&.target
343 on the created mount unit, e\&.g\&.
344 local\-fs\&.target, are not automatically created\&. Hence it is likely that some ordering dependencies need to be set up manually through
345 \fBx\-systemd\&.before=\fR
346 and
347 \fBx\-systemd\&.after=\fR\&. See
348 \fIWantedBy=\fR
349 and
350 \fIRequiredBy=\fR
351 in
352 \fBsystemd.unit\fR(5)
353 for details\&.
354 .sp
355 Added in version 245\&.
356 .RE
357 .PP
358 \fBx\-systemd\&.wants\-mounts\-for=\fR, \fBx\-systemd\&.requires\-mounts\-for=\fR
359 .RS 4
360 Configures a
361 \fIRequiresMountsFor=\fR
362 or
363 \fIWantsMountsFor=\fR
364 dependency between the created mount unit and other mount units\&. The argument must be an absolute path\&. This option may be specified more than once\&. See
365 \fIRequiresMountsFor=\fR
366 or
367 \fIWantsMountsFor=\fR
368 in
369 \fBsystemd.unit\fR(5)
370 for details\&.
371 .sp
372 Added in version 220\&.
373 .RE
374 .PP
375 \fBx\-systemd\&.graceful\-option=\fR
376 .RS 4
377 Additional mount option that shall be appended if supported by the kernel\&. This may be used to configure mount options that are optional and only enabled on kernels that support them\&. Note that this is supported only for native kernel mount options (i\&.e\&. explicitly not for mount options implemented in userspace, such as those processed by
378 \fB/usr/bin/mount\fR
379 itself, by FUSE or by mount helpers such as
380 \fBmount\&.nfs\fR)\&. This option may be specified more than once\&.
381 .sp
382 Added in version 258\&.
383 .RE
384 .PP
385 \fBx\-systemd\&.device\-bound=\fR
386 .RS 4
387 Takes a boolean argument\&. If true or no argument, a
388 \fIBindsTo=\fR
389 dependency on the backing device is set\&. If false, the mount unit is not stopped no matter whether the backing device is still present\&. This is useful when the file system is backed by volume managers\&. If not set, and the mount comes from unit fragments, i\&.e\&. generated from
390 /etc/fstab
391 by
392 \fBsystemd-fstab-generator\fR(8)
393 or loaded from a manually configured mount unit, a combination of
394 \fIRequires=\fR
395 and
396 \fIStopPropagatedFrom=\fR
397 dependencies is set on the backing device, otherwise only
398 \fIRequires=\fR
399 is used\&.
400 .sp
401 Added in version 233\&.
402 .RE
403 .PP
404 \fBx\-systemd\&.automount\fR
405 .RS 4
406 An automount unit will be created for the file system\&. See
407 \fBsystemd.automount\fR(5)
408 for details\&.
409 .sp
410 Added in version 215\&.
411 .RE
412 .PP
413 \fBx\-systemd\&.idle\-timeout=\fR
414 .RS 4
415 Configures the idle timeout of the automount unit\&. See
416 \fITimeoutIdleSec=\fR
417 in
418 \fBsystemd.automount\fR(5)
419 for details\&.
420 .sp
421 Added in version 220\&.
422 .RE
423 .PP
424 \fBx\-systemd\&.device\-timeout=\fR
425 .RS 4
426 Configure how long systemd should wait for a device to show up before giving up on an entry from
427 /etc/fstab\&. Specify a time in seconds or explicitly append a unit such as
428 "s",
429 "min",
430 "h",
431 "ms"\&.
432 .sp
433 Note that this option can only be used in
434 /etc/fstab, and will be ignored when part of the
435 \fIOptions=\fR
436 setting in a unit file\&.
437 .sp
438 Added in version 215\&.
439 .RE
440 .PP
441 \fBx\-systemd\&.mount\-timeout=\fR
442 .RS 4
443 Configure how long systemd should wait for the mount command to finish before giving up on an entry from
444 /etc/fstab\&. Specify a time in seconds or explicitly append a unit such as
445 "s",
446 "min",
447 "h",
448 "ms"\&.
449 .sp
450 Note that this option can only be used in
451 /etc/fstab, and will be ignored when part of the
452 \fIOptions=\fR
453 setting in a unit file\&.
454 .sp
455 See
456 \fITimeoutSec=\fR
457 below for details\&.
458 .sp
459 Added in version 233\&.
460 .RE
461 .PP
462 \fBx\-systemd\&.makefs\fR
463 .RS 4
464 The file system will be initialized on the device\&. If the device is not "empty", i\&.e\&. it contains any signature, the operation will be skipped\&. It is hence expected that this option remains set even after the device has been initialized\&.
465 .sp
466 Note that this option can only be used in
467 /etc/fstab, and will be ignored when part of the
468 \fIOptions=\fR
469 setting in a unit file\&.
470 .sp
471 See
472 \[email protected]\fR(8)\&.
473 .sp
474 \fBwipefs\fR(8)
475 may be used to remove any signatures from a block device to force
476 \fBx\-systemd\&.makefs\fR
477 to reinitialize the device\&.
478 .sp
479 Added in version 236\&.
480 .RE
481 .PP
482 \fBx\-systemd\&.growfs\fR
483 .RS 4
484 The file system will be grown to occupy the full block device\&. If the file system is already at maximum size, no action will be performed\&. It is hence expected that this option remains set even after the file system has been grown\&. Only certain file system types are supported, see
485 \[email protected]\fR(8)
486 for details\&.
487 .sp
488 Note that this option can only be used in
489 /etc/fstab, and will be ignored when part of the
490 \fIOptions=\fR
491 setting in a unit file\&.
492 .sp
493 Added in version 236\&.
494 .RE
495 .PP
496 \fBx\-systemd\&.pcrfs\fR
497 .RS 4
498 Measures file system identity information (mount point, type, label, UUID, partition label, partition UUID) into PCR 15 after the file system has been mounted\&. This ensures the
499 \[email protected]\fR(8)
500 or
501 systemd\-pcrfs\-root\&.service
502 services are pulled in by the mount unit\&.
503 .sp
504 Note that this option can only be used in
505 /etc/fstab, and will be ignored when part of the
506 \fIOptions=\fR
507 setting in a unit file\&. It is also implied for the root and
508 /usr/
509 partitions discovered by
510 \fBsystemd-gpt-auto-generator\fR(8)\&.
511 .sp
512 Added in version 253\&.
513 .RE
514 .PP
515 \fBx\-systemd\&.validatefs\fR
516 .RS 4
517 Validates mount constraint metadata of the mounted file system after mounting it\&. This ensures the
518 \[email protected]\fR(8)
519 service is pulled in by the mount unit\&.
520 .sp
521 Note that this option can only be used in
522 /etc/fstab, and will be ignored when part of the
523 \fIOptions=\fR
524 setting in a unit file\&. It is also implied for all partitions discovered by
525 \fBsystemd-gpt-auto-generator\fR(8)\&.
526 .sp
527 Added in version 258\&.
528 .RE
529 .PP
530 \fBx\-systemd\&.rw\-only\fR
531 .RS 4
532 If a mount operation fails to mount the file system read\-write, it normally tries mounting the file system read\-only instead\&. This option disables that behaviour, and causes the mount to fail immediately instead\&. This option is translated into the
533 \fIReadWriteOnly=\fR
534 setting in a unit file\&.
535 .sp
536 Added in version 246\&.
537 .RE
538 .PP
539 \fB_netdev\fR
540 .RS 4
541 Normally the file system type is used to determine if a mount is a "network mount", i\&.e\&. if it should only be started after the network is available\&. Using this option overrides this detection and specifies that the mount requires network\&.
542 .sp
543 Network mount units are ordered between
544 remote\-fs\-pre\&.target
545 and
546 remote\-fs\&.target, instead of
547 local\-fs\-pre\&.target
548 and
549 local\-fs\&.target\&. They also pull in
550 network\-online\&.target
551 and are ordered after it and
552 network\&.target\&.
553 .sp
554 Added in version 235\&.
555 .RE
556 .PP
557 \fBnoauto\fR, \fBauto\fR
558 .RS 4
559 With
560 \fBnoauto\fR, the mount unit will not be added as a dependency for
561 local\-fs\&.target
562 or
563 remote\-fs\&.target\&. This means that it will not be mounted automatically during boot, unless it is pulled in by some other unit\&. The
564 \fBauto\fR
565 option has the opposite meaning and is the default\&.
566 .sp
567 Note that if
568 \fBx\-systemd\&.automount\fR
569 (see above) is used, neither
570 \fBauto\fR
571 nor
572 \fBnoauto\fR
573 have any effect\&. The matching automount unit will be added as a dependency to the appropriate target\&.
574 .sp
575 Added in version 215\&.
576 .RE
577 .PP
578 \fBnofail\fR
579 .RS 4
580 With
581 \fBnofail\fR, this mount will be only wanted, not required, by
582 local\-fs\&.target
583 or
584 remote\-fs\&.target\&. Moreover, the mount unit is not ordered before these target units\&. This means that the boot will continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully\&.
585 .sp
586 Added in version 215\&.
587 .RE
588 .PP
589 \fBx\-initrd\&.mount\fR
590 .RS 4
591 An additional filesystem to be mounted in the initrd\&. See
592 initrd\-fs\&.target
593 description in
594 \fBsystemd.special\fR(7)\&. This is both an indicator to the initrd to mount this partition early and an indicator to the host to leave the partition mounted until final shutdown\&. Or in other words, if this flag is set it is assumed the mount shall be active during the entire regular runtime of the system, i\&.e\&. established before the initrd transitions into the host all the way until the host transitions to the final shutdown phase\&.
595 .sp
596 Added in version 215\&.
597 .RE
598 .PP
599 If a mount point is configured in both
600 /etc/fstab
601 and a unit file that is stored below
602 /usr/, the former will take precedence\&. If the unit file is stored below
603 /etc/, it will take precedence\&. This means: native unit files take precedence over traditional configuration files, but this is superseded by the rule that configuration in
604 /etc/
605 will always take precedence over configuration in
606 /usr/\&.
607 .SH "OPTIONS"
608 .PP
609 Mount unit files may include [Unit] and [Install] sections, which are described in
610 \fBsystemd.unit\fR(5)\&.
611 .PP
612 Mount unit files must include a [Mount] section, which carries information about the file system mount points it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
613 \fBsystemd.exec\fR(5),
614 \fBsystemd.kill\fR(5)
615 and
616 \fBsystemd.resource-control\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
617 .PP
618 \fIWhat=\fR
619 .RS 4
620 Takes an absolute path or a fstab\-style identifier of a device node, file or other resource to mount\&. See
621 \fBmount\fR(8)
622 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
623 \fBsystemd.device\fR(5)
624 for more information\&.) This option is mandatory\&. Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as
625 "%%"\&. If this mount is a bind mount and the specified path does not exist yet it is created as directory\&.
626 .RE
627 .PP
628 \fIWhere=\fR
629 .RS 4
630 Takes an absolute path of a file or directory for the mount point; in particular, the destination cannot be a symbolic link\&. If the mount point does not exist at the time of mounting, it is created as either a directory or a file\&. The former is the usual case; the latter is done only if this mount is a bind mount and the source (\fIWhat=\fR) is not a directory\&. This string must be reflected in the unit filename\&. (See above\&.) This option is mandatory\&.
631 .RE
632 .PP
633 \fIType=\fR
634 .RS 4
635 Takes a string for the file system type\&. See
636 \fBmount\fR(8)
637 for details\&. This setting is optional\&.
638 .sp
639 If the type is
640 "overlay", and
641 "upperdir="
642 or
643 "workdir="
644 are specified as options and the directories do not exist, they will be created\&.
645 .RE
646 .PP
647 \fIOptions=\fR
648 .RS 4
649 Mount options to use when mounting\&. This takes a comma\-separated list of options\&. This setting is optional\&. Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as
650 "%%"\&.
651 .RE
652 .PP
653 \fISloppyOptions=\fR
654 .RS 4
655 Takes a boolean argument\&. If true, parsing of the options specified in
656 \fIOptions=\fR
657 is relaxed, and unknown mount options are tolerated\&. This corresponds with
658 \fBmount\fR(8)\*(Aqs
659 \fI\-s\fR
660 switch\&. Defaults to off\&.
661 .sp
662 Added in version 215\&.
663 .RE
664 .PP
665 \fILazyUnmount=\fR
666 .RS 4
667 Takes a boolean argument\&. If true, detach the filesystem from the filesystem hierarchy at time of the unmount operation, and clean up all references to the filesystem as soon as they are not busy anymore\&. This corresponds with
668 \fBumount\fR(8)\*(Aqs
669 \fI\-l\fR
670 switch\&. Defaults to off\&.
671 .sp
672 Added in version 232\&.
673 .RE
674 .PP
675 \fIReadWriteOnly=\fR
676 .RS 4
677 Takes a boolean argument\&. If false, a mount point that shall be mounted read\-write but cannot be mounted so is retried to be mounted read\-only\&. If true the operation will fail immediately after the read\-write mount attempt did not succeed\&. This corresponds with
678 \fBmount\fR(8)\*(Aqs
679 \fI\-w\fR
680 switch\&. Defaults to off\&.
681 .sp
682 Added in version 246\&.
683 .RE
684 .PP
685 \fIForceUnmount=\fR
686 .RS 4
687 Takes a boolean argument\&. If true, force an unmount (in case of an unreachable NFS system)\&. This corresponds with
688 \fBumount\fR(8)\*(Aqs
689 \fI\-f\fR
690 switch\&. Defaults to off\&.
691 .sp
692 Added in version 232\&.
693 .RE
694 .PP
695 \fIDirectoryMode=\fR
696 .RS 4
697 Directories of mount points (and any parent directories) are automatically created if needed\&. This option specifies the file system access mode used when creating these directories\&. Takes an access mode in octal notation\&. Defaults to 0755\&.
698 .RE
699 .PP
700 \fITimeoutSec=\fR
701 .RS 4
702 Configures the time to wait for the mount command to finish\&. If a command does not exit within the configured time, the mount will be considered failed and be shut down again\&. All commands still running will be terminated forcibly via
703 \fBSIGTERM\fR, and after another delay of this time with
704 \fBSIGKILL\fR\&. (See
705 \fBKillMode=\fR
706 in
707 \fBsystemd.kill\fR(5)\&.) Takes a unit\-less value in seconds, or a time span value such as "5min 20s"\&. Pass 0 to disable the timeout logic\&. The default value is set from
708 \fIDefaultTimeoutStartSec=\fR
709 option in
710 \fBsystemd-system.conf\fR(5)\&.
711 .RE
712 .PP
713 Check
714 \fBsystemd.unit\fR(5),
715 \fBsystemd.exec\fR(5), and
716 \fBsystemd.kill\fR(5)
717 for more settings\&.
718 .SH "SEE ALSO"
719 .PP
720 \fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.device\fR(5), \fBproc\fR(5), \fBmount\fR(8), \fBsystemd-fstab-generator\fR(8), \fBsystemd.directives\fR(7), \fBsystemd-mount\fR(1)
721 .SH "NOTES"
722 .IP " 1." 4
723 API File Systems
724 .RS 4
725 \%https://systemd.io/API_FILE_SYSTEMS
726 .RE