Using systemd is way better than fstab even though it requires way more work. Systemd can automatically mount it when the server is available.
Also why are you using sshfs? Wouldn't it be simpler to go the Samba route?
this post was submitted on 16 Feb 2024
28 points (91.2% liked)
Selfhosted
39226 readers
388 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Autofs works with sshfs. I use it for mounting anything over a network. It automounts on demand and disconnects a mount after a period of inactivity.
Plus one for autofs, works so well that I often forget that certain files are actually remote resources
Write a systemd service, that's how my computers mount my nas. you just need to have it run under your user instead of root or point it towards the right keys manually.
And consider adding a timeout, or else all your devices will take and additional 2 minutes to boot if the server is offline and the mount fails.
I just have them check for my wifi. If that's what they're connected to, then the nas is available. If not, then there's no point trying to mount it. However, one day every month my nas pulls updates and shuts down afterwards, so that I need to boot it again when I get home from work. But my laptop boots just as fast as it normally does, even though it fails to connect to the nas.
store all of the documents, desktop, downloads, etc. on a couple computers
Why use SSHFS for that? I recommend using Syncthing, it's great for synchronizing stuff across multiple PCs (local and remote).
Why use SSHFS for that?
So that you don't have copies of files everywhere.
What do you mean "everywhere"?
everywhere you want to use the files.
I don't really know what that is. I could try it though.
Edit: I don't really like having the files on all computers, I would rather just have them all in a central place where everything can access them.
I'm on OpenRC, so I can't say anything about systemd, but I have several SSHFS mounts (non-auto) listed in my fstab:
sshfs#root@192.168.0.123:/random-folder/ /mnt/random-folder fuse noauto,uid=1000,gid=100,allow_other 0 0
Is that similar to what you've tried in your fstab? I'd assume replacing noauto with auto should just work, but then again, I haven't tried it (and rebooting my system right now would be very inconvenient, sorry).
It also might require you to either use password-based login and specify the password or store the SSH keys in the .ssh directory of the user doing the mount (should be root with auto set).
I already have SSH keys set up but auto doesn't work. I think fstab mounts things before network is up.
I do this already using systemd service (well technically OpenRC script, but I doubt you're using openRC. Systemd is equivalent).
I run Debian 12 and ran into similar issues trying to automount NFS, even down to having to use an alternative console to log in and undo f stab edits
My solution was simple and so hopefully it helps you as well. In fstab, the backslashes don't cancel out spaces. Since my directory path had a space in it, that would break fstab:
Path/to/your/Video\ Files breaks fstab
Path/to/your/VideoFiles good