FS#71650 - Manual SSHFS mounts defined in /etc/fstab fail
Attached to Project:
Arch Linux
Opened by David Parrish (dmp1ce) - Thursday, 29 July 2021, 11:48 GMT
Last edited by Christian Heusel (gromit) - Monday, 28 August 2023, 08:41 GMT
Opened by David Parrish (dmp1ce) - Thursday, 29 July 2021, 11:48 GMT
Last edited by Christian Heusel (gromit) - Monday, 28 August 2023, 08:41 GMT
|
Details
Description:
I had several fuse.sshfs mounts defined in /etc/fstab but they all stopped working after a recent update. My /etc/fstab lines look like this: david@server:/home/david/VideoProjects /mnt/server/VideoProjects fuse.sshfs noauto,defaults,_netdev,idmap=user 0 0 I normally could `mount /mnt/serer/VideoProjects` and the sshfs mount works. When I try `mount /mnt/serer/VideoProjects` now the command immediately returns to the prompt with a 1 return code. Additional info: Attached is my pacman.log just before the mounts stopped working. I couldn't find any upstream issues. Steps to reproduce: 1. Setup a network sshfs mount using fstab. 2. Try to manually mount the sshfs network mount using the `mount` command. |
This task depends upon
Closed by Christian Heusel (gromit)
Monday, 28 August 2023, 08:41 GMT
Reason for closing: Fixed
Additional comments about closing: User reports that the problem is gone
Monday, 28 August 2023, 08:41 GMT
Reason for closing: Fixed
Additional comments about closing: User reports that the problem is gone
vault@sftp.server.com:/users/vault/ /mnt/something/ sshfs workaround=rename,noauto,user 0 0
I also attached an excerpt of pacman.log, covering the latest update.
@David Parrish: Maybe you have a different issue, but could you check the permissions of /dev/fuse right after boot? Maybe some udev rules of yours started interfering with the device too.
I attached relevant `journalctl -b` results.