@pid_eins Does systems-remount-fs not like /dev/mapper paths? Switching to a different disk for boot/root on a ubuntu 22.04 system and I used that type of path for / in fstab and it didn't give errors on boot but didn't remount as rw either which was not helpful. Changed to a /dev/disk/by-uuid/ path and now it's working ...
=> More informations about this toot | More toots from acsawdey@fosstodon.org
@acsawdey systemd-remount-fs is mostly a wrapper around /bin/mount, and calls it in parallel for the root fs, for /usr/ and for the API VFS (i.e. /sys/, /proc/, …).
Hence, there's barely any logic in systemd-remount-fs, it just forks of children in paralell that run /bin/mount commands and waits for them to finish.
Or in other words: if there's an issue here it's probably in /bin/mount, not in systemd...
(But I never heard of an issue like yours before)
=> More informations about this toot | More toots from pid_eins@mastodon.social
@pid_eins Yeah that’s kind of the conclusion I came to after poking at it with strace and staring at the source. It looks like there is an env var that’s passed to tell it to add “rw” to the mount options in addition to remount, I couldn’t tell where that gets generated.
=> More informations about this toot | More toots from acsawdey@fosstodon.org This content has been proxied by September (3851b).Proxy Information
text/gemini