Am 23.01.2018 um 20:09 schrieb Mike Gilbert:
On Tue, Jan 23, 2018 at 10:54 AM, Reindl Harald <h.rei...@thelounge.net> wrote:
Am I right in thinking this is only done if the filesystem is not declared
as noauto in fstab?
with Fedora 27 (yesterday upgraded) systemd even don't leave "noauto"
mount-point in peace and spits the "Failed to read symlink target for
/mnt/arrakis: Permission denied" for fuse-mountpoints multiple times each
day into the systemlogs (systemd-234-9.fc27.x86_64)
[root@srv-rhsoft:~]$ systemctl daemon-reload
[root@srv-rhsoft:~]$ cat messages
Jan 23 16:52:16 srv-rhsoft systemd-fstab-generator[27644]: Failed to read
symlink target for /mnt/arrakis: Permission denied
[root@srv-rhsoft:~]$ cat /etc/fstab | grep /mnt/arrakis
sshfs#reindl@arrakis:/ /mnt/arrakis fuse
noauto,user,rw,noexec,nosuid,nodev,noatime,uid=harry
Sounds like you have a broken symlink at /mnt or /mnt/arrakis. systemd
is trying to deference said symlink when it generates the mount unit
for that fstab entry
no - it's how fuse-mountpoints simply work
nobody but the user which mounted is has access and hence systemd should
leave fuse-mountpoints with "noauto" completly in peace as well as any
"noauto" stuff or manual mounted filesystems
you can see mount-unit failures on CentOS7 as example when you unmount
your manually mounted luks-on-raid10 storage with no entry in fstab at all
[root@srv-rhsoft:~]$ stat /mnt/arrakis
stat: cannot stat '/mnt/arrakis': Permission denied
[harry@srv-rhsoft:~]$ stat /mnt/arrakis
File: /mnt/arrakis
Size: 16384 Blocks: 32 IO Block: 4096 directory
Device: 48h/72d Inode: 1 Links: 1
Access: (0755/drwxr-xr-x) Uid: ( 500/ harry) Gid: ( 501/verwaltung)
Access: 2018-01-23 21:15:02.000000000 +0100
Modify: 2017-12-21 15:07:12.000000000 +0100
Change: 2017-12-21 15:07:12.000000000 +0100
Birth: -
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
