On Mon, May 5, 2025 at 10:03 AM Andrei Borzenkov <arvidj...@gmail.com> wrote:
> On Mon, May 5, 2025 at 4:58 PM Kaizaad Bilimorya <kaiz...@sharcnet.ca> > wrote: > > > > Hello Silvio, > > Thank you for your response. > > We're using Ansible to automate some tasks so it is easier (and more > reliable) to add/remove mount unit files than having to parse the fstab for > our specific mount options. > > And as the Systemd documentation says "For tooling, writing mount units > should be preferred over editing /etc/fstab" which is something I agree > with. I need the > > "x-initrd.mount" option since we are setting up some custom Dracut hooks > early in the boot process for the local disk and want this disk mounted > before switch-root. > > > > You do not need "x-initrd.mount". Isn't the purpose of the "x-initrd.mount" option to have a filesystem mounted in the initrd? Which is what I need. > You need to add your unit to initrd. > I guess that is an option but why wouldn't I just use the "x-initrd.mount" option if that is available? How did you expect to achieve it with a string in the unit definition? I didn't expect anything, I was just reporting that it would be nice if the documentation was consistent since this option works fine in fstab. thanks -k