diff options
| author | Lennart Poettering <lennart@poettering.net> | 2022-12-09 16:08:54 +0100 |
|---|---|---|
| committer | Luca Boccassi <luca.boccassi@gmail.com> | 2022-12-10 11:26:36 +0100 |
| commit | 09e917ea4dd6f00aa3cb225072f6991a637227e1 (patch) | |
| tree | 0f208e93dcec1484b3e9ec86931a59e31e863f4e /man/repart.d.xml | |
| parent | mount-setup: don't need to mount /sys/fs/pstore if there is no ENABLE_PSTORE (diff) | |
| download | systemd-09e917ea4dd6f00aa3cb225072f6991a637227e1.tar.xz systemd-09e917ea4dd6f00aa3cb225072f6991a637227e1.zip | |
repart: support erofs
So, i think "erofs" is probably the better, more modern alternative to
"squashfs". Many of the benefits don't matter too much to us I guess,
but there's one thing that stands out: erofs has a UUID in the
superblock, squashfs has not. Having an UUID in the superblock matters
if the file systems are used in an overlayfs stack, as overlayfs uses
the UUIDs to robustly and persistently reference inodes on layers in
case of metadata copy-up.
Since we probably want to allow such uses in overlayfs as emplyoed by
sysext (and the future syscfg) we probably should ramp up our erofs game
early on. Hence let's natively support erofs, test it, and in fact
mention it in the docs before squashfs even.
Diffstat (limited to 'man/repart.d.xml')
| -rw-r--r-- | man/repart.d.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/man/repart.d.xml b/man/repart.d.xml index fe3de8d58a..d5ce3f8587 100644 --- a/man/repart.d.xml +++ b/man/repart.d.xml @@ -383,12 +383,13 @@ <term><varname>Format=</varname></term> <listitem><para>Takes a file system name, such as <literal>ext4</literal>, <literal>btrfs</literal>, - <literal>xfs</literal>, <literal>vfat</literal>, <literal>squashfs</literal>, or the special value - <literal>swap</literal>. If specified and the partition is newly created it is formatted with the - specified file system (or as swap device). The file system UUID and label are automatically derived - from the partition UUID and label. If this option is used, the size allocation algorithm is slightly - altered: the partition is created as least as big as required for the minimal file system of the - specified type (or 4KiB if the minimal size is not known).</para> + <literal>xfs</literal>, <literal>vfat</literal>, <literal>erofs</literal>, + <literal>squashfs</literal> or the special value <literal>swap</literal>. If specified and the partition + is newly created it is formatted with the specified file system (or as swap device). The file system + UUID and label are automatically derived from the partition UUID and label. If this option is used, + the size allocation algorithm is slightly altered: the partition is created as least as big as + required for the minimal file system of the specified type (or 4KiB if the minimal size is not + known).</para> <para>This option has no effect if the partition already exists.</para> |