Unable to unmount

[tooadstool]

I don't know when this phenomenon started to appear: Mount points already mounted(I can access the files on the server.), but the interface does not display "mounted" or the "unmount" button.

[bobrofon]

Mount points already mounted

I guess, it might be mounted, but not accessible for any application not running as root.

Can you try to specify /mnt/runtime/default/emulated/0/neobackup instead of /storage/emulated/0/neobackup in the mountpoint settings?

Also, as a quick workaround, you can always use mount/umount menu options in the mountpoint edit screen:

[tooadstool]

I guess, it might be mounted, but not accessible for any application not running as root.

but Google Files APP (no root) can access the files

Can you try to specify /mnt/runtime/default/emulated/0/neobackup instead of /storage/emulated/0/neobackup in the mountpoint settings?

when i specify /mnt/runtime/default/emulated/0/neobackup instead of /storage/emulated/0/neobackup , can‘t mount.

[bobrofon]

but Google Files APP (no root) can access the files

Could you share grep neobackup /proc/$(pgrep easysshfs)/mounts output when the folder is mounted (without sensitive info, like ip)?

when i specify /mnt/runtime/default/emulated/0/neobackup instead of /storage/emulated/0/neobackup , can‘t mount

That's strange. What OS (and version) are you using?

[tooadstool]

Could you share grep neobackup /proc/$(pgrep easysshfs)/mounts output when the folder is mounted (without sensitive info, like ip)?

It seems there is no output.

by the way, when it mounted, the APP "Solid Explorer" (with root) can access the files from /sdcard/neobackup, but can not access the files from /mnt/runtime/default/emulated/0/neobackup.

That's strange. What OS (and version) are you using?

Pixel 7 Pro Android 15 (BP1A.250505.005.B1)

[tooadstool]

I don't know when this phenomenon started to appear:

I thought about it again, and it seems to have happened after I switched from APATCH to Wild KSU, but I'm not entirely sure.

[bobrofon]

I thought about it again, and it seems to have happened after I switched from APATCH to Wild KSU, but I'm not entirely sure.

Possible. Easysshfs relies on a feature provided by some Android root shells, sometimes called "disabling mount namespace separation" (in SuperSU), or "master mount" (in Magisk). Basically, it's the ability to run a shell inside Zygote's mount namespace, which allows new mount points to be propagated to all Android applications. Without this, mounting still works, but some applications may not see it.

Technically, easysshfs could move mount operations to another namespace by itself, without any support from the root shell, but I haven't tried it.