From b750101eb236130cf056c675997decbac904cc49 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 17:35:18 +0200 Subject: Adding upstream version 252.22. Signed-off-by: Daniel Baumann --- man/systemd-makefs@.service.xml | 103 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 103 insertions(+) create mode 100644 man/systemd-makefs@.service.xml (limited to 'man/systemd-makefs@.service.xml') diff --git a/man/systemd-makefs@.service.xml b/man/systemd-makefs@.service.xml new file mode 100644 index 0000000..1eedb77 --- /dev/null +++ b/man/systemd-makefs@.service.xml @@ -0,0 +1,103 @@ + + + + + + + + systemd-makefs@.service + systemd + + + + systemd-makefs@.service + 8 + + + + systemd-makefs@.service + systemd-mkswap@.service + systemd-growfs@.service + systemd-growfs-root.service + systemd-makefs + systemd-growfs + Creating and growing file systems on demand + + + + systemd-makefs@device.service + systemd-mkswap@device.service + systemd-growfs@mountpoint.service + systemd-growfs-root.service + /usr/lib/systemd/systemd-makefs + /usr/lib/systemd/systemd-growfs + + + + Description + + systemd-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 Also + + systemd1, + systemd.mount8, + systemd-fstab-generator8, + systemd-repart8, + mkfs.btrfs8, + mkfs.cramfs8, + mkfs.ext48, + mkfs.fat8, + mkfs.hfsplus8, + mkfs.minix8, + mkfs.ntfs8, + mkfs.xfs8 + + + + -- cgit v1.2.3