Unable to mount SSHFS directory with rw permission

Question

I have a directory on a CentOS 7.6 machine that I want to mount on another machine that runs RedHat 7.9.

On the RedHat machine, I add this line to /etc/fstab:

[email protected]:/mnt/Scan-PDF /mnt/scanfiles/ fuse.sshfs rw,x-systemd.automount,x-systemd.nofail,_netdev,idmap=user,allow_other,transform_symlinks,identityfile=/root/.ssh/id_rsa,umask=0222     0 0

I have been trying various options such as uid, user, etc. The result is the same in that the filesystem is mounted as read-only. The file /proc/mounts shows two entries (why 2?):

systemd-1 /mnt/scanfiles autofs rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=26826 0 0
[email protected]:/mnt/Scan-PDF /mnt/scanfiles fuse.sshfs ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0

Answer 1

It looks like the filesystem is being mounted as read-only, which could be causing issues with accessing or modifying files on the remote system.

One thing to check is the permissions on the remote directory (/mnt/Scan-PDF). Make sure that the user on the local machine has appropriate permissions to read and write to the directory.

Another thing to try is to add the "rw" option to the mount command in /etc/fstab:

[email protected]:/mnt/Scan-PDF /mnt/scanfiles/ fuse.sshfs rw,x-systemd.automount,x-systemd.nofail,_netdev,idmap=user,allow_other,transform_symlinks,identityfile=/root/.ssh/id_rsa,umask=0222 0 0

Also, try removing the "ro" option from the mount command and see if that helps:

[email protected]:/mnt/Scan-PDF /mnt/scanfiles/ fuse.sshfs nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,rw,transform_symlinks,identityfile=/root/.ssh/id_rsa,umask=0222 0 0

After making changes to /etc/fstab, you can try remounting the filesystem using the command "mount -a" to see if the changes take effect.

Answer 2

Found the issue.

SYSTEMD creates automount files for entries found in fstab that are mounted using systemd-mount

In my case, the file /proc/mounts was showing 2 entries for the same item. Giving the umount command once was unmouting only one of them and remounting was just adding the entry without doing an actual mount operation. I umounted both. Thereafter, mount worked as expected.