Hello there,
Question related to the file system setup of fcos.
I defined a partition within ignition on the install device.
disks:
- device: /dev/nvme0n1
wipe_table: false
partitions:
- label: DATA
start_mib: 0
number: 0
size_mib: 10240
As well as the filesystem:
filesystems:
- device: /dev/disk/by-partlabel/DATA
format: ext4
path: /mnt/data
wipe_filesystem: false
label: data
My goal would be that after the setup my disk looks like this:
The reason for putting my own partition in front of the system partitions, would be that
if I re execute ignition on this device
the defined partition should not be erased and possible to expand with a new ignition
file. The sysroot partition should get all the remaining space.
nvme0n1 259:0 0 238.5G 0 disk
|-nvme0n1p1 259:5 0 10G 0 part /mnt/data
|-nvme0n1p2 259:1 0 384M 0 part /boot
|-nvme0n1p3 259:2 0 127M 0 part /boot/efi
|-nvme0n1p4 259:3 0 1M 0 part
|-nvme0n1p5 259:4 0 225.8G 0 part /sysroot
But because of some it currently looks like this. When adding the filesystems as defined
above my ignition will fail on first boot.
nvme0n1 259:0 0 238.5G 0 disk
|-nvme0n1p1 259:1 0 384M 0 part /boot
|-nvme0n1p2 259:2 0 127M 0 part /boot/efi
|-nvme0n1p3 259:3 0 1M 0 part
|-nvme0n1p4 259:4 0 2.1G 0 part /sysroot
`-nvme0n1p5 259:5 0 10G 0 part
If I would run it with just the disks defined I can run the ignition but the file system
will be erased each time.
I tested it by manually adding the filesystem: sudo mount -t auto -v /dev/nvme0n1p5
/mnt/data
this will return an error and expects me to redo: mkfs.ext4 /dev/nvme0n1p5
Is there any way to define a partition which won't get lost after a re execution of
ignition?