1SYSTEMD-MAKEFS@.SERVICE(8) systemd-makefs@.service SYSTEMD-MAKEFS@.SERVICE(8)
2
3
4
6 systemd-makefs@.service, systemd-makeswap@.service, systemd-
7 growfs@.service, systemd-makefs, systemd-growfs - Creating and growing
8 file systems on demand
9
11 systemd-makefs@device.service
12
13 systemd-makeswap@device.service
14
15 systemd-growfs@mountpoint.service
16
17 /usr/lib/systemd/systemd-makefs
18
19 /usr/lib/systemd/systemd-growfs
20
22 systemd-makefs@.service, systemd-makeswap@.service, and
23 systemd-growfs@.service are used to implement the x-systemd.makefs and
24 x-systemd.growfs options in fstab(5), see systemd.mount(5). They are
25 instantiated for each device for which the file system or swap
26 structure needs to be initialized, and for each mount point where the
27 file system needs to be grown.
28
29 These services are started at boot, either right before or right after
30 the mount point or swap device are used.
31
32 systemd-makefs knows very little about specific file systems and swap
33 devices, and after checking that the block device does not already
34 contain a file system or other content, it will execute binaries
35 specific to each filesystem type (/sbin/mkfs.*).
36
37 systemd-growfs knows very little about specific file systems and swap
38 devices, and will instruct the kernel to grow the mounted filesystem to
39 full size of the underlying block device. Nevertheless, it needs to
40 know the ioctl(2) number specific to each file system, so only certain
41 types are supported. Currently: ext4(5), btrfs (see btrfs-man5(5)), and
42 dm-crypt partitions (see cryptsetup(8)).
43
44 If the creation of a file system or swap device fails, the mount point
45 or swap is failed too. If the growing of a file system fails, a warning
46 is emitted.
47
49 systemd(1), systemd.mount(8), systemd-fstab-generator(8),
50 mkfs.btrfs(8), mkfs.cramfs(8), mkfs.ext4(8), mkfs.fat(8),
51 mkfs.hfsplus(8), mkfs.minix(8), mkfs.ntfs(8), mkfs.xfs(8)
52
53
54
55systemd 239 SYSTEMD-MAKEFS@.SERVICE(8)