Debian Codegraph @

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

raw
1 '\" t
2 .TH "SYSTEMD\&.MOUNT" "5" "" "systemd 257.13" "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\&.device\-bound=\fR
376 .RS 4
377 Takes a boolean argument\&. If true or no argument, a
378 \fIBindsTo=\fR
379 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
380 /etc/fstab
381 by
382 \fBsystemd-fstab-generator\fR(8)
383 or loaded from a manually configured mount unit, a combination of
384 \fIRequires=\fR
385 and
386 \fIStopPropagatedFrom=\fR
387 dependencies is set on the backing device, otherwise only
388 \fIRequires=\fR
389 is used\&.
390 .sp
391 Added in version 233\&.
392 .RE
393 .PP
394 \fBx\-systemd\&.automount\fR
395 .RS 4
396 An automount unit will be created for the file system\&. See
397 \fBsystemd.automount\fR(5)
398 for details\&.
399 .sp
400 Added in version 215\&.
401 .RE
402 .PP
403 \fBx\-systemd\&.idle\-timeout=\fR
404 .RS 4
405 Configures the idle timeout of the automount unit\&. See
406 \fITimeoutIdleSec=\fR
407 in
408 \fBsystemd.automount\fR(5)
409 for details\&.
410 .sp
411 Added in version 220\&.
412 .RE
413 .PP
414 \fBx\-systemd\&.device\-timeout=\fR
415 .RS 4
416 Configure how long systemd should wait for a device to show up before giving up on an entry from
417 /etc/fstab\&. Specify a time in seconds or explicitly append a unit such as
418 "s",
419 "min",
420 "h",
421 "ms"\&.
422 .sp
423 Note that this option can only be used in
424 /etc/fstab, and will be ignored when part of the
425 \fIOptions=\fR
426 setting in a unit file\&.
427 .sp
428 Added in version 215\&.
429 .RE
430 .PP
431 \fBx\-systemd\&.mount\-timeout=\fR
432 .RS 4
433 Configure how long systemd should wait for the mount command to finish before giving up on an entry from
434 /etc/fstab\&. Specify a time in seconds or explicitly append a unit such as
435 "s",
436 "min",
437 "h",
438 "ms"\&.
439 .sp
440 Note that this option can only be used in
441 /etc/fstab, and will be ignored when part of the
442 \fIOptions=\fR
443 setting in a unit file\&.
444 .sp
445 See
446 \fITimeoutSec=\fR
447 below for details\&.
448 .sp
449 Added in version 233\&.
450 .RE
451 .PP
452 \fBx\-systemd\&.makefs\fR
453 .RS 4
454 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\&.
455 .sp
456 Note that this option can only be used in
457 /etc/fstab, and will be ignored when part of the
458 \fIOptions=\fR
459 setting in a unit file\&.
460 .sp
461 See
462 \[email protected]\fR(8)\&.
463 .sp
464 \fBwipefs\fR(8)
465 may be used to remove any signatures from a block device to force
466 \fBx\-systemd\&.makefs\fR
467 to reinitialize the device\&.
468 .sp
469 Added in version 236\&.
470 .RE
471 .PP
472 \fBx\-systemd\&.growfs\fR
473 .RS 4
474 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
475 \[email protected]\fR(8)
476 for details\&.
477 .sp
478 Note that this option can only be used in
479 /etc/fstab, and will be ignored when part of the
480 \fIOptions=\fR
481 setting in a unit file\&.
482 .sp
483 Added in version 236\&.
484 .RE
485 .PP
486 \fBx\-systemd\&.pcrfs\fR
487 .RS 4
488 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
489 \[email protected]\fR(8)
490 or
491 systemd\-pcrfs\-root\&.service
492 services are pulled in by the mount unit\&.
493 .sp
494 Note that this option can only be used in
495 /etc/fstab, and will be ignored when part of the
496 \fIOptions=\fR
497 setting in a unit file\&. It is also implied for the root and
498 /usr/
499 partitions discovered by
500 \fBsystemd-gpt-auto-generator\fR(8)\&.
501 .sp
502 Added in version 253\&.
503 .RE
504 .PP
505 \fBx\-systemd\&.rw\-only\fR
506 .RS 4
507 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
508 \fIReadWriteOnly=\fR
509 setting in a unit file\&.
510 .sp
511 Added in version 246\&.
512 .RE
513 .PP
514 \fB_netdev\fR
515 .RS 4
516 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\&.
517 .sp
518 Network mount units are ordered between
519 remote\-fs\-pre\&.target
520 and
521 remote\-fs\&.target, instead of
522 local\-fs\-pre\&.target
523 and
524 local\-fs\&.target\&. They also pull in
525 network\-online\&.target
526 and are ordered after it and
527 network\&.target\&.
528 .sp
529 Added in version 235\&.
530 .RE
531 .PP
532 \fBnoauto\fR, \fBauto\fR
533 .RS 4
534 With
535 \fBnoauto\fR, the mount unit will not be added as a dependency for
536 local\-fs\&.target
537 or
538 remote\-fs\&.target\&. This means that it will not be mounted automatically during boot, unless it is pulled in by some other unit\&. The
539 \fBauto\fR
540 option has the opposite meaning and is the default\&.
541 .sp
542 Note that if
543 \fBx\-systemd\&.automount\fR
544 (see above) is used, neither
545 \fBauto\fR
546 nor
547 \fBnoauto\fR
548 have any effect\&. The matching automount unit will be added as a dependency to the appropriate target\&.
549 .sp
550 Added in version 215\&.
551 .RE
552 .PP
553 \fBnofail\fR
554 .RS 4
555 With
556 \fBnofail\fR, this mount will be only wanted, not required, by
557 local\-fs\&.target
558 or
559 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\&.
560 .sp
561 Added in version 215\&.
562 .RE
563 .PP
564 \fBx\-initrd\&.mount\fR
565 .RS 4
566 An additional filesystem to be mounted in the initrd\&. See
567 initrd\-fs\&.target
568 description in
569 \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\&.
570 .sp
571 Added in version 215\&.
572 .RE
573 .PP
574 If a mount point is configured in both
575 /etc/fstab
576 and a unit file that is stored below
577 /usr/, the former will take precedence\&. If the unit file is stored below
578 /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
579 /etc/
580 will always take precedence over configuration in
581 /usr/\&.
582 .SH "OPTIONS"
583 .PP
584 Mount unit files may include [Unit] and [Install] sections, which are described in
585 \fBsystemd.unit\fR(5)\&.
586 .PP
587 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
588 \fBsystemd.exec\fR(5),
589 \fBsystemd.kill\fR(5)
590 and
591 \fBsystemd.resource-control\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
592 .PP
593 \fIWhat=\fR
594 .RS 4
595 Takes an absolute path or a fstab\-style identifier of a device node, file or other resource to mount\&. See
596 \fBmount\fR(8)
597 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
598 \fBsystemd.device\fR(5)
599 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
600 "%%"\&. If this mount is a bind mount and the specified path does not exist yet it is created as directory\&.
601 .RE
602 .PP
603 \fIWhere=\fR
604 .RS 4
605 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\&.
606 .RE
607 .PP
608 \fIType=\fR
609 .RS 4
610 Takes a string for the file system type\&. See
611 \fBmount\fR(8)
612 for details\&. This setting is optional\&.
613 .sp
614 If the type is
615 "overlay", and
616 "upperdir="
617 or
618 "workdir="
619 are specified as options and the directories do not exist, they will be created\&.
620 .RE
621 .PP
622 \fIOptions=\fR
623 .RS 4
624 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
625 "%%"\&.
626 .RE
627 .PP
628 \fISloppyOptions=\fR
629 .RS 4
630 Takes a boolean argument\&. If true, parsing of the options specified in
631 \fIOptions=\fR
632 is relaxed, and unknown mount options are tolerated\&. This corresponds with
633 \fBmount\fR(8)\*(Aqs
634 \fI\-s\fR
635 switch\&. Defaults to off\&.
636 .sp
637 Added in version 215\&.
638 .RE
639 .PP
640 \fILazyUnmount=\fR
641 .RS 4
642 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
643 \fBumount\fR(8)\*(Aqs
644 \fI\-l\fR
645 switch\&. Defaults to off\&.
646 .sp
647 Added in version 232\&.
648 .RE
649 .PP
650 \fIReadWriteOnly=\fR
651 .RS 4
652 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
653 \fBmount\fR(8)\*(Aqs
654 \fI\-w\fR
655 switch\&. Defaults to off\&.
656 .sp
657 Added in version 246\&.
658 .RE
659 .PP
660 \fIForceUnmount=\fR
661 .RS 4
662 Takes a boolean argument\&. If true, force an unmount (in case of an unreachable NFS system)\&. This corresponds with
663 \fBumount\fR(8)\*(Aqs
664 \fI\-f\fR
665 switch\&. Defaults to off\&.
666 .sp
667 Added in version 232\&.
668 .RE
669 .PP
670 \fIDirectoryMode=\fR
671 .RS 4
672 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\&.
673 .RE
674 .PP
675 \fITimeoutSec=\fR
676 .RS 4
677 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
678 \fBSIGTERM\fR, and after another delay of this time with
679 \fBSIGKILL\fR\&. (See
680 \fBKillMode=\fR
681 in
682 \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
683 \fIDefaultTimeoutStartSec=\fR
684 option in
685 \fBsystemd-system.conf\fR(5)\&.
686 .RE
687 .PP
688 Check
689 \fBsystemd.unit\fR(5),
690 \fBsystemd.exec\fR(5), and
691 \fBsystemd.kill\fR(5)
692 for more settings\&.
693 .SH "SEE ALSO"
694 .PP
695 \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)
696 .SH "NOTES"
697 .IP " 1." 4
698 API File Systems
699 .RS 4
700 \%https://systemd.io/API_FILE_SYSTEMS
701 .RE