|Summary:||fuse (bindfs) filesystems are unmounted upon network disconnect (even if non-networked)|
|Product:||Gentoo Hosted Projects||Reporter:||Jacopo <jacopods>|
|Component:||OpenRC||Assignee:||OpenRC Team <openrc>|
|Package list:||Runtime testing required:||---|
Description Jacopo 2019-03-01 06:23:42 UTC
the openrc configuration variable $net_fs_list hardcodes the item "fuse", which is used by some filesystems not necessarily on network mounts (e.g. bindfs) This causes such mounts to be killed when network is unavailable (e.g. airplane mode). Reproducible: Always
Comment 1 Florian Gamböck 2019-07-14 11:24:59 UTC
I can confirm that this behavior is still present. By putting bindfs mounts into fstab like so: /home/floga/Sync/root /mnt/sync/root fuse.bindfs create-for-user=floga,create-for-group=floga,chown-ignore,chgrp-ignore,force-user=root,force-group=root 0 0 What happens at boot time is, localmount will mount these mountpoints automatically, because "fuse.bindfs" is not in net_fs_list. However, once mounted, bindfs mounts advertise their types as simply "fuse" (maybe a limitation of FUSE itself?). Therefore, if the network goes down, netmount will unmount them because "fuse" IS in net_fs_list. If the network comes up again, netmount will NOT mount them again, because, as previously noted, "fuse.bindfs" is NOT in net_fs_list. If the network never comes up again, the remount won't even be tried. So in each case we are left with the directories unmounted although they are not dependant of a network connection. How can we mitigate this issue? Maybe via a whitelist, so we can globally declare FUSE as "not a network mount"?