[SOLVED] Prevent racy mounting when booting

ball · 2014-01-22 17:18:20

Hey there!

When booting I mount an external (encrypted) drive by the means of fstab (and crypttab) under a directory which is only accessible by root. In order to allow read-only access for users, I remount the the device under another directory which allows reading for ordinary users by the means of bindfs.

The relevant part of my /etc/fstab goes like this:

/dev/mapper/backup /mnt/root/backup ext4 defaults 0 2
bindfs#/mnt/root/backup /mnt/backup fuse perms=a-w 0 0

However, after booting up the contents of /mnt/root/backup do not show up under /mnt/backup. Remounting /mnt/backup manually makes the files appear. I suspect that this is because the bindfs mounting is done before mounting /mnt/root/backup has finished; also the order of the two mounts shown when issuing the mount command is inverted to the order in fstab.

How do I have to cope with this situation?

Shall I add noauto to the bindfs instruction and write a custom service file for systemd in order to mount the read-only ressource at a later time? (I am asking this because I am fairly unexperienced when in comes to systemd and I don't want to head for the wrong track...)

Last edited by ball (2014-01-22 18:36:25)

WorMzy · 2014-01-22 18:07:11

See this topic regarding how to write bindfs fstab entries: https://bbs.archlinux.org/viewtopic.php?id=175230

ball · 2014-01-22 18:39:02

Thanks, this is solved. (But it's a bit frustrating that this is not documented in bindfs(1) -- I've reported it upstream.)

Arch Linux

#1 2014-01-22 17:18:20

[SOLVED] Prevent racy mounting when booting

#2 2014-01-22 18:07:11

Re: [SOLVED] Prevent racy mounting when booting

#3 2014-01-22 18:39:02

Re: [SOLVED] Prevent racy mounting when booting

Board footer