Zen

Translation Read only

English type: delimited block -
[Install]
WantedBy=multi-user.target
0/530 · 53

The string is read only.

English Chinese (Simplified) (zh_CN) Actions
Sizing the root partition
 
If you use Ignition to reconfigure or move the root partition, that partition is not automatically grown on first boot (see related discussions in https://github.com/coreos/fedora-coreos-tracker/issues/570[this issue]). In the case of moving the root partition to a new disk (or multiple disks), you should set the desired partition size using the `size_mib` field. If reconfiguring the root filesystem in place, as in the LUKS example above, you can resize the existing partition using the `resize` field:
 
Resizing the root partition to its maximum size
 
variant: fcos
version: {butane-latest-stable-spec}
storage:
disks:
- device: /dev/disk/by-id/coreos-boot-disk
partitions:
- label: root
number: 4
# 0 means to use all available space
size_mib: 0
resize: true
luks:
- name: root
device: /dev/disk/by-partlabel/root
clevis:
tpm2: true
wipe_volume: true
filesystems:
- device: /dev/mapper/root
format: xfs
wipe_filesystem: true
label: root
 
Adding swap
 
This example creates a swap partition spanning all of the `sdb` device, creates a swap area on it, and creates a systemd swap unit so the swap area is enabled on boot.
 
Configuring a swap partition on a second disk
 
variant: fcos
version: {butane-latest-stable-spec}
storage:
disks:
- device: /dev/sdb
wipe_table: true
partitions:
- number: 1
label: swap
filesystems:
- device: /dev/disk/by-partlabel/swap
format: swap
wipe_filesystem: true
with_mount_unit: true
 
Adding network storage
 
Fedora CoreOS systems can be configured to mount network filesystems such as NFS and CIFS. This is best achieved by using Ignition to create systemd units. Filesystems can be mounted on boot by creating a standard mount unit. Alternatively, a filesystem can be mounted when users access the mountpoint by creating an additional automount unit. Below are examples of each for an NFS filesystem.
 
Configuring NFS mounts
 
Creating a systemd unit to mount an NFS filesystem on boot.
 
The `.mount` file must be named based on the path (e.g. `/var/mnt/data` = `var-mnt-data.mount`)
 
variant: fcos
version: 1.3.0
systemd:
units:
- name: var-mnt-data.mount
enabled: true
contents: |
[Unit]
Description=Mount data directory
 
[Mount]
What=example.org:/data
Where=/var/mnt/data
Type=nfs4
 
[Install]
WantedBy=multi-user.target
 
Creating a systemd unit to mount an NFS filesystem when users access the mount point (automount)
 
variant: fcos
version: 1.3.0
systemd:
units:
- name: var-mnt-data.mount
contents: |
[Unit]
Description=Mount data directory
 
- name: var-mnt-data.automount
enabled: true
contents: |
[Unit]
Description=Automount data directory
 
[Automount]
TimeoutIdleSec=20min
Where=/var/mnt/data
 
Advanced examples
 
This example configures a mirrored boot disk with a TPM2-encrypted root filesystem, overrides the sizes of the automatically-generated root partition replicas, and adds an encrypted mirrored `/var` partition which consumes the remainder of the disks.
 
Encrypted mirrored boot disk with separate /var
 
variant: fcos
version: {butane-latest-stable-spec}
boot_device:
luks:
tpm2: true
mirror:
devices:
- /dev/sda
- /dev/sdb
storage:
disks:
- device: /dev/sda
partitions:
# Override size of root partition on first disk, via the label
# generated for boot_device.mirror
- label: root-1
size_mib: 10240
# Add a new partition filling the remainder of the disk
- label: var-1
- device: /dev/sdb
partitions:
# Similarly for second disk
- label: root-2
size_mib: 10240
- label: var-2
raid:
- name: md-var
level: raid1
devices:
- /dev/disk/by-partlabel/var-1
- /dev/disk/by-partlabel/var-2
luks:
- name: var
device: /dev/md/md-var
# No key material is specified, so a random key will be generated
# and stored in the root filesystem
filesystems:
- device: /dev/mapper/var
path: /var
label: var
format: xfs
wipe_filesystem: true
with_mount_unit: true
 
Disk Layout
 
All Fedora CoreOS systems start with the same disk image which varies slightly between architectures based on what is needed for bootloading. On first boot the root filesystem is expanded to fill the rest of the disk. The disk image can be customized using Butane configs to repartition the disk and create/reformat filesystems. Bare metal installations are not different; the installer only copies the raw image to the target disk and injects the specified config into `/boot` for use on first boot.
 
See xref:#_reconfiguring_the_root_filesystem[Reconfiguring the root filesystem] for examples regarding the supported changes to the root partition.
 
Partition Tables
 
Using partition numbers to refer to specific partitions is discouraged and labels or UUIDs should be used instead. Fedora CoreOS reserves the `boot`, `boot-<number>`, `root`, `root-<number>`, `BIOS-BOOT`, `bios-<number>`, `EFI-SYSTEM`, and `esp-<number>` labels, and the `md-boot` and `md-root` RAID device names. Creating partitions, filesystems, or RAID devices with those labels is not supported.
 
x86_64 Partition Table
 
The x86_64 disk image is GPT formatted with a protective MBR. It supports booting via both BIOS and UEFI (including Secure Boot).
 

Loading…

No matching activity found.
Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English Chinese (Simplified) (zh_CN)
No related strings found in the glossary.

8894512 String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
pages/storage.adoc:463 • pages/storage.adoc:484 • pages/storage.adoc:497
String age
3 years ago
Last updated
a year ago
Source string age
3 years ago
Translation file
po/zh_CN/master/pages/storage.po, string 83