Dolphin - fstab sshfs mount support

Help
1

Hi,

I have sshfs mounts in fstab. Is there any support for this in Dolphin? In Gnome Files, I can see them under Other Locations.

Fedora 37
Dolphin 22.12.3

Thanks.

2

Just drag the location you’ve mounted it into the sidebar like any other folder I believe.

3

The thing is that I have them in fstab with noauto, I have too many to mount them all so I just mount the ones that I work on on a specific day. I do the same with nfs mounts in fstab and they show up fine in Dolphin under Remote. I don’t understand why I can’t get the same behavior with sshfs.

Thanks for your help.

4

I guess that is missing is someone who implement the behavior (Maybe you :wink: )

5

I wish I had the skills :expressionless:

At least now I know that it’s not something that I did not setup properly. I’ll submit to https://bugs.kde.org/ in wishlist and hope it makes it’s way on a future release.

Thanks again!

6

Oh if you don’t have them auto-mounting just create shortcuts in the Dolphin sidebar. The location syntax is just fish://my-server/home/me for example.

7

I tried that and it’s not the same as a mount. Most software can’t open files from it and don’t handle the path correctly.

8

I guess I’ve only ever used it to transfer files and edit the odd text file and I’ve had no issues. You seem to be stuck between a rock and a hard place :slight_smile:

9

See People keep manually mounting network shares, causing hangs, and then blaming KDE code for it (#71) · Issues · Plasma / Plasma Desktop · GitLab.

1 Like
10

As far as I know, there is no KIO slave for sshfs (and fish is not a good replacement).

1 Like
11

Blaming KDE is correct there, IMO. Native Linux network mounts, fuse mounts, etc., are totally normal, and KDE should be handling them gracefully. For one thing, I/O should not be blocking the UI rendering, so there should be no hangs. For another thing, IIRC Dolphin does have a capability to tread lightly on slow filesystems (in terms of # of syscalls, listing extra directories, etc.), but it it seems not to be wired up unless the slow filesystem is accessed by kio.

But most slow filesystems are not accessed by kio. Standard Practice, if someone wants to make an adapter for an exotic file system, is to make a FUSE backend, not a kio backend.

Examples abound. sshfs, as used by kdeconnect. borg mount, which leaks memory when you look inside directories (see borgbackup github issue #2407, #issuecomment-412036637 by ThomasWaldmann on Aug 10, 2018). Spun-down mechanical hard drives, which stall the UI for 7 seconds if you make the mistake of viewing a directory with a symlink to one. I looked for bugs, and “Dolphin lags if it gets within 10 feet of a slow filesystem” is a known problem.

Like, if Dolphin parsed /proc/mounts and used a whitelist of fast filesystems to enable all of the aggressive thumbnailing, child-directory-contents counting, and stat()-ing, that’d be way better. Better still would be another layer of filter on top of that, to turn it off again if any I/O operation takes longer than 200 ms. That covers things like cross-country iSCSI.

4 Likes
12

I just noticed that it’s been implemented in Version 24.12.0. Just need to figure out the order now, I have lots of mounts.

13

So with respect, nfs doesn’t work, sshfs doesn’t work, wth then works? (Don’t even mention samba-lambada which is Microshaft trashbloat, we are GNU/Linux here)

Using fish doesn’t even work, if you enter fish://theusername@theremotehostname (or the ip) you get a “No hostname specified” …