Unstable Mounting on Rooted Pixel Device (Android 10) after Recent Update

[sjpatel21]

I am using the app on rooted Pixel device for quite some time now, and it seems that the mounting has become quite unstable after the recent update.

My phone sits next to the wifi and always on charge, but the connection will drop unexpectedly and unmount/mount would not work and the only option left is to reboot the device.

Device info Model: Pixel 1 OS: Stock Android 10 Magisk Version: 27.0 App Version: 0.5.11

Please let me know if you want me to debug/try something. Thanks for your awesome work.

Logs:

>_ mount
>_ubuntu@192.168.50.160:/media/issd/photos/testsshfs: No such file or directory
> _ exit code: 1
>_ Pattern /testsshfs ubuntu@192.168.50.160:/media/issd/photos /mnt/runtime/default/emulated/0/DCIM fuse.sshfs is not in /proc/mounts
>_ umount -l -v /mnt/runtime/default/emulated/0/DCIM
>_ umount: can't unmount /mnt/runtime/default/emulated/0/ DCIM: Invalid argument
>_ exit code: 1
>_ Pattern ubuntu@192.168.50.160:/media/issd/photos/sunny /testsshfs /mnt/runtime/default/emulated/0/DCIM fuse.sshfs is not in /proc/mounts
>_ Pattern ubuntu@192.168.50.160:/media/xboxdrive/photos /sunny/mnt/runtime/default/emulated/0/DCIM/Xboxdrive fuse.sshfs is not in /proc/mounts
>_ Pattern ubuntu@192.168.50.160:/media/issd/photos/sunny /testsshfs/mnt/runtime/default/emulated/0/DCIM fuse.sshfs is not in /proc/mounts
>_ mount
>_ exit code: 0
>_ Pattern ubuntu@192.168.50.160:/media/issd/photos/sunny /testsshfs /mnt/runtime/default/emulated/0/DCIM fuse.sshfs is in/proc/mounts
>_ Pattern ubuntu@192.168.50.160:/media/xboxdrive/photos /sunny/mnt/runtime/default/emulated/0/DCIM/Xboxdrive fuse.sshfs is not in /proc/mounts
>_ Pattern ubuntu@192.168.50.160:/media/issd/photos/sunny
/testsshfs/mnt/runtime/default/emulated/0/DCIM fuse.sshfs is not in /proc/mounts
>_ mount
>_ exit code: 0
>_ Pattern ubuntu@192.168.50.160:/media/issd/photos/sunny /testsshfs/mnt/runtime/default/emulated/0/DCIM fuse.sshfs is in /proc/mounts

[bobrofon]

the mounting has become quite unstable after the recent update

By the "recent update", do you mean "upgrading from easysshfs from version 0.5.10 to 0.5.11"? Or was something else changed? As far as I can see, the only change in the latest release was a workaround to avoid one of the issues with Magisk 27.0. And it shouldn't affect mount stability in any way.

Magisk Version: 27.0 App Version: 0.5.11

Can you try downgrading both Magisk and easysshfs to their previous versions to confirm that the issue is specific to certain versions of these apps (and not related to some changes in the environment)?

[bobrofon]

the only option left is to reboot the device

killall ssh should also help, if you have access to the terminal. I guess it's a slightly better workaround than rebooting.

[sjpatel21]

@bobrofon yes by "recent update" I meant Magisk 27.0 and EasySSHFS 0.5.11 Will try killall ssh next time. Thanks, that would indeed be a better workaround. Is there a way to generate more informative logs for debug purposes?

[bobrofon]

Is there a way to generate more informative logs for debug purposes?

I'm not sure that any application logs will be helpful here. Based on your description, it seems like the problem is not related to any ssh/sshfs/fuse/easysshfs logic. And it's more likely something related to Android itself (like power or network managers are doing something with the network) or the environment. In that case adb bugreport may help. However, it contains a lot of unnecessary information about the system, and I'm unsure where I should start looking for a problem anyway.

The more interesting information is that previously the mountpoints were stable. This could be because in the last version of Magisk, some workaround was removed, or due to some other factor. So, experimenting with different system configurations and application versions should provide much more information about the problem.

[bobrofon]

@sjpatel21 Can you also try adding something like reconnect,ServerAliveInterval=5,ServerAliveCountMax=3 to the mountpoint's options?

[sjpatel21]

@bobrofon Will add these lines and reply back.