Hello, I am using Manjaro XFCE and try to mount a directory with FFHS. I’m using the following entry in /etc/fstab from the example of the Arch wiki . *user*@*host*:*/remote/path /local/path* fuse.sshfs noauto,x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/*user*/.ss…

Hi @vommie , I’m guessing this happens because everything in fstab gets mounted as root when the system starts up. According to this page you can change that by setting the uid and gid options for the mount. So changing it to: *user*@*host*:*/remote/path /local/path* fuse.sshfs noauto,x-systemd.aut…

Hey @Mirdarthos , thanks for your answer. I already showed in the example and wrote in the text below that I’ve set the uid and gid. And as you can see in the fstab example, there is an x-systemd.automount which does, as the Wiki page says, “does the magic”. But I’ve tried it with a systemd service …

Create the mount point manually, while the mount isn’t active. That should make it persistent. (Or that’s how mine is anyway. Also make sure that it’s not mounted somewhere volatile, like /run or /tmp.)

Thanks again. I already tried to remove the mount directory, it get’s recreated but it’s root:root again. It seems the fstab ignores the uid and gid. But I don’t get why (or if this is really the case). If I run the command “id” I get this info: uid=1000(vommie) gid=1001(vommie) groups=1001(vommie…

[image] vommie: /run/media/vommie/temp That’s specifically what I advised against: [image] Mirdarthos: make sure that it’s not mounted somewhere volatile, like /run or /tmp. …because /tmp is RAM, and AFAIK /run gets recreated at boot and if it’s the same on every boot, it’s pure luck …

[image] vommie: fusermount3: user has no write access to mountpoint /run/media/user/foldername Probably because systemd-automount does not create the whole directory? As I know it just creates the last folder, so if /run/media is there, then it will not create /run/media/username/mountpoint, …

Thanks for your efforts, but the problem in my opinion is not the location (which is used in every Arch article and automatically by the system for mounts), nor that the folder is removed or recreated at boot time, nor the access rights, but simply that the user “vommie” is not assigned while the sh…

According to the Linux Foundation : /run /run is another new directory. System processes use it to store temporary data for their own nefarious reasons. This is another one of those DO NOT TOUCH folders. [image] vommie: automatically Yes. Not by humans. [image] vommie: the user “vomm…

A hint that it makes more sense to mount somewhere else is ok, but you’re acting like that’s the problem, which it definitely is not. "Pure luck … sure. The fstab dices. And just for your info: I’ve changed the mount dir and the problem persists. Weird … how can this be? Seems /run was not the prob…

I’m thinking permissions. Ownership, user and group, and permissions. Both of the mountpoint, as well as the contents of the mounts.

Manjaro Linux Forum

Fusermount3: user has no mount access to mountpoint (SSHFS)

Support

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled