The mountpoint is /home/joy/dai
The remote mountpoint was accessed and connected by
sshfs -o idmap=user -o reconnect hps@ath:/dai/sand /home/joy/dai
The server ath is offline now. And now, after reboot systemd tells me
journalctl -xe -u home-joy-dai.mount
Mär 05 20:51:38 TP15 systemd[1]: home-joy-dai.mount: Deactivated successfully.
Subject: Unit succeeded
Defined-By: systemd
Support: systemd-devel Info Page **
**
The unit home-joy-dai.mount has successfully entered the ‘dead’ state.
The device systemtray pops up at the same time, interrupting any regular workflow.
The messages from journalctl -xe -u home-joy-dai.mount are two minutes apart. Every 6min there are 2 messagas 4sec apart..
Each time the device systemtray shows a network share entry for a short moment:
~/dai on fuse.sshfs.
Sofar “nothing” helped to stop that zombie:
fusermount3 -zu dai, rmdir dai, sudo umount -f /home/joy/dai. All nice Gemini “I am thinking” results were worth less.
Killing /usr/bin/kdeconnectd and /usr/sbin/restorecond -u in a desperate action -no effect.
There are no more entries in fstab, mtab. No hint in dmesg.
Searching in /tmp and /var for dai and fuse.sshfs, I found one, probably relevant entry:
/var/spool/clientmqueue/df41OAo1Me093754
::800 64 0:69 / /home/joy/dai rw,nosuid,nodev,relatime shared:1136 - fus=
e.sshfs hps@ath:/dai/sand rw,user_id=3D1000,group_id=3D1000
I removed that entry. Reboot included. The zombie keeps komming back.
What I am looking for:
systemd does not have a home-joy-dai.mount unit but says Defined-By: systemd.
How das it happen?
Where does systemd get the string home-joy-dai from?
What command checks on hps@ath:…, finds out that ath is not there and then happily shouting at systemd or device system tray - nothing there-?
What is this hidden link from user / KDE / sshfs to root / systemd?
How to find, catch the origin of home-joy-dai in systemd?
Any idea on how to end that reconnect zombe is welcome, except reinstall:-)