systemd-makefs@.servicesystemdsystemd-makefs@.service8systemd-makefs@.servicesystemd-mkswap@.servicesystemd-growfs@.servicesystemd-growfs-root.servicesystemd-makefssystemd-growfsCreating and growing file systems on demandsystemd-makefs@device.servicesystemd-mkswap@device.servicesystemd-growfs@mountpoint.servicesystemd-growfs-root.service/usr/lib/systemd/systemd-makefs/usr/lib/systemd/systemd-growfsDescriptionsystemd-makefs@.service,
systemd-mkswap@.service,
systemd-growfs@.service, and
systemd-growfs-root.service are used to implement the
and options
in fstab5,
see systemd.mount5.
They are instantiated for each device for which the file system or swap structure
needs to be initialized, and for each mount point where the file system needs to
be grown.These services are started at boot, either right before or right after the
mount point or swap device are used.systemd-makefs knows very little about specific file
systems and swap devices, and after checking that the block device does not already
contain a file system or other content, it will execute binaries specific to
each filesystem type (/sbin/mkfs.type
or /sbin/mkswap). For certain file system types (currently
ext2/ext3/ext45,
btrfs5,
xfs5,
f2fs, vfat) and for swap devices, it will configure reasonable defaults and set
the file system label and UUID based on the device name.systemd-growfs knows very little about specific file
systems and swap devices, and will instruct the kernel to grow the mounted
filesystem to full size of the underlying block device. Nevertheless, it needs
to know the
ioctl2
number specific to each file system, so only certain types are supported.
Currently:
ext45,
btrfs5,
xfs5,
and dm-crypt partitions (see
cryptsetup8).
If the creation of a file system or swap device fails, the mount point or
swap is failed too. If the growing of a file system fails, a warning is emitted.
See Alsosystemd1systemd.mount8systemd-fstab-generator8systemd-repart8mkfs.btrfs8mkfs.cramfs8mkfs.ext48mkfs.fat8mkfs.hfsplus8mkfs.minix8mkfs.ntfs8mkfs.xfs8