Kickstart file to customize rootfs mount opts not modifying fstab as expected

Kickstart file to customize rootfs mount opts not modifying fstab as expected

[Iván Castell]

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

Hello forum.

I want to customize my rootfs partition to be mounted with the
"data=journal" option enabled.

To do that I have modified my layer adding a custom mkefidisk.wks script
with this contents for the rootfs partition:

    part / --source rootfs --ondisk sda --fstype=ext4
--fsoptions="data=journal" --label platform --use-uuid --size 80000 --align
1024

According to yocto reference manual:

    https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html

The --fsoptions option specifies a free-form string of options to be used
when mounting the filesystem. This string will be copied into the
/etc/fstab file of the installed system and should be enclosed in quotes.
If not specified, the default string is "defaults".

I expected to find a /etc/fstab with "data=journal" on the mounted rootfs.
However, after mounting .ext4 image, this is the /etc/fstab content for the
rootfs partition:

    /dev/root            /                    auto       defaults
    1  1

As you can see, it doesn't contain any reference to "data=journal".

What is wrong with that?

Thanks in advance.

Regards,
  -- Ivan

[-- Attachment #2: Type: text/html, Size: 1755 bytes --]

Re: Kickstart file to customize rootfs mount opts not modifying fstab as expected

[Iván Castell]

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

After some googling I fixed my issue customizing mkefidisk.wks script, adding
"rootflags=data=journal" to the line related with the bootloader:

    bootloader --ptable gpt --timeout=5 --append="rootfstype=ext4
console=ttyS0,115200 console=tty0 rootflags=data=journal noapic"

Now my rootfs is mounted with "journal" flag enabled:

    # mount | grep sda
    /dev/sda3 on / type ext4 (rw,relatime,nodelalloc,data=journal)

I don't know if this is the most proper way to manage this issue, but at
least it works now.

If some of you knows a better way to manage this, please let me know about
it.

Thank you in advance! :)

[-- Attachment #2: Type: text/html, Size: 1293 bytes --]