There was a discussion on the linux-btrfs mailing list about this, and for example the btrfs space_cache option can not be changed with a remount - this causes the fstab file's space_cache option to be basically ignored. I want to eliminate this kind of issue on my setup, that's why I need to avoid root being remounted. Instead I want root to be mounted with the options specified in fstab the first (and only) time. On 20 January 2016 at 20:56, Devon Smith <devo8604@xxxxxxxxx> wrote: > According to this page: > http://www.freedesktop.org/software/systemd/man/systemd-remount-fs.service.html > > The systemd remount service remounts your root file system according > to what is listed in fstab. This includes mounting root with the mount > options listed therein. > > If you need something else, what exactly are you trying to do? > > Devon > > On Wed, Jan 20, 2016 at 12:16 PM, Garmine 42 <mikro001@xxxxxxxxx> wrote: >> Hi! >> >> My concern is that there are a few mount flags which can not be >> changed with a remount (at least on some FSes such as btrfs). >> >> Now as far as I understand, the kernel mounts root RO after boot using >> the root and rootflags parameters. I also found that you can include >> /etc/fstab in the initrd. How can I convince the kernel to mount every >> volume including the root according to fstab instead of the kernel >> paramters? >> >> In case the kernel isn't the one which reads fstab (which I suspect), >> can I include some binary in the initrd that would read fstab and >> handle the mounting for me? >> >> Or should I just scrap the whole above idea and write something >> that'll a) read the root volume's options from fstab and put it on the >> cmdline through e.g. a grub-mkconfig script? >> >> Thanks in advance! >> >> Regards, >> Garmine
