Steps to reproduce:
1. Open a native ThinLinc client and export two local directories that start with the same letter(s), for example 'Documents' and 'Downloads'.
4. Reconnect using the HTML5 client
5. Open a terminal and write: ls ~/thindrives/Do
6. Press TAB
One such application is tl-setup. restorecon (part of the SELinux step) will take forever to complete if there are a bunch of disconnected drives.
(In reply to comment #2)
> One such application is tl-setup. restorecon (part of the SELinux step) will
> take forever to complete if there are a bunch of disconnected drives.
Split off to bug #7075.
This also affects other users, not just the user with the unreachable drive. E.g. doing df on such a system hangs. This can be very annoying for the system administrator.
systemd also gets upset about this and has problem starting certain services. E.g. localectl stops working because the underlying service fails to start in time.
More details about systemd:
This can also cause a session to take some time to terminate if there are previous sessions that didn't get unmounted properly:
> tl-xinit: X server has terminated
> tl-xinit: deleting ../10.1604999466.ended
> tl-xinit: cannot stat ../10.1604999466.ended/drives/notes: Input/output error
> tl-xinit: Could not remove ../10.1604999466.ended. Stray files may remain.
> tl-xinit: deleting ../10.1605087058.ended
> tl-xinit: Session terminated. Exiting.
The delay can cause issues if users try to reconnect too quickly as they'll be reconnected to this terminating session instead, which won't actually work.
Unfortunately we don't know what caused these mounts to remain and trigger the issue.
*** Bug 1271 has been marked as a duplicate of this bug. ***