Root filesystem options in /etc/fstab are not respected by openrc-0.3.0-r1 on machines without inird. I have this line in /etc/fstab: /dev/xvda1 / ext3 noatime,acl 0 1 'mount' command shows: rootfs on / type rootfs (rw) /dev/root on / type ext3 (rw,errors=continue,data=ordered) /proc/mounts contains: /dev/root / ext3 rw,errors=continue,data=ordered 0 0 Service /etc/init.d/root has 'started' status. Re-running command "mount -n -o remount,rw /" (from /etc/init.d/root) results in updated /proc/mounts with correct filesystem options, but 'mount' command still gives old results (as mtab was not updated). It is strange that root filesystem device is referred as /dev/root instead of /dev/xvda1. My other machines which use initrd to initialize LVM haven't this problem. Reproducible: Always Steps to Reproduce:
Ok, found the issue - if kernel mounts the filesystem as read-write, openrc doesn't try to remount it with correct filesystem options. Keeping bug open, as it may need either fixing openrc or adding note to documentation.
Also probably thes same bug - why I have two lines for /: # mount rootfs on / type rootfs (rw) /dev/sdb2 on / type ext3 (rw,noatime,errors=continue,data=ordered) # cat /proc/mounts rootfs / rootfs rw 0 0 /dev/sdb2 / ext3 rw,noatime,errors=continue,data=ordered 0 0 I have only one line in my fstab for /: /dev/sdb2 / ext3 noatime 0 1 I'm using openrc-0.4.2
If you have your kernel setup to mount your root as rw this won't work on any distro. All check to see if root is rw and will only remount if it's not. Basically the solution here, is either don't have the kernel mount your root partition rw or setup the proper mount settings with tune2fs so the kernel mounts it with the correct settings.
