https://bugs.kde.org/show_bug.cgi?id=433611
Méven <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |CONFIRMED Ever confirmed|0 |1 CC| |[email protected] See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=423187, | |https://bugs.kde.org/show_b | |ug.cgi?id=441077, | |https://bugs.kde.org/show_b | |ug.cgi?id=445065, | |https://bugs.kde.org/show_b | |ug.cgi?id=503995 --- Comment #11 from Méven <[email protected]> --- (In reply to daniel_moelders from comment #3) > Created attachment 178140 [details] > Trace with gdb #0 __GI___fstatat64 (fd=-100, file=0x5555562120f0 "/mnt/truenas/service_data", buf=0x7fffffffc1e0, flag=256) at ../sysdeps/unix/sysv/linux/fstatat64.c:159 r = -512 #1 0x00007ffff7940b43 in KMountPoint::possibleMountPoints (infoNeeded=..., infoNeeded@entry=...) at /usr/src/debug/kio/kio-6.10.0/src/core/kmountpoint.cpp:194 We don't have a way from the system perspective to know in advance whether a filesystem is "working" i.e accessible or not beforehand. Or at least I don't know how to do that. A potential complicated solution is to use libiouring since it allows to do asynchrouns syscalls and cancel them. statvfs is not one handled. https://bugs.kde.org/show_bug.cgi?id=423187 https://bugs.kde.org/show_bug.cgi?id=441077 https://bugs.kde.org/show_bug.cgi?id=445065 https://bugs.kde.org/show_bug.cgi?id=503995 -- You are receiving this mail because: You are watching all bug changes.
