SUMMARY When accessing a Windows DFS share through kio, dolphin complains about not enough space in the destination copying data to the share. Running "df" on the kio mount confirms that there are 0 bytes reported free, and the reported file system size is also 0 bytes. From cmdline, files can still be created or copied. Accessing the same share directly from the DFS member reports correct sizes and allows dolphin to copy files to the share. Mounting DFS directly via CIFS kernel support reports the correct values. SMB shares: \\domain.local\DFS\Storage -> 0 bytes free and 0 bytes size \\member1.domain.local\Storage -> sizes reported correctly \\member2.domain.local\Storage -> also reported correctly STEPS TO REPRODUCE 1. Setup a DFS share with two member servers and DFSR sync 2. Access share via DFS share via kio to check for free space 3. Access share directly on member server via kio to check for free space OBSERVED RESULT kio-smb reports 0 bytes free and 0 bytes file system size, preventing kio clients from writing data due to out of space condition (actually, it may complain about insufficient permissions sometimes but that's not true, it's still "out of space"). EXPECTED RESULT kio-smb should report file system stats correctly for DFS shares. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.1.26-gentoo (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 Manufacturer: ASRock Product Name: Z690 Pro RS
Please provide reproducible steps for 1. Setup a DFS share with two member servers and DFSR sync
(In reply to Harald Sitter from comment #1) > Please provide reproducible steps for 1. Setup a DFS share with two member > servers and DFSR sync On two Windows Server hosts, install DFS replication services. Install DFS namespace services on at least one host and setup a DFS namespace using the first two hosts as target servers. Then create a replication group between those two members to keep the shares in sync. I'm not sure if DFS replication is actually necessary to show the 0-space-bug, it may be sufficient to use a single DFS target without replication, and just point kio-smb to access the share through the DFS namespace, although using DFS with a single target share is not really that useful.
Not exactly the level of detail I wanted but it'll do :) And you are quite certain this is with kio-extras 23.04?
(In reply to Harald Sitter from comment #3) > Not exactly the level of detail I wanted but it'll do :) > > And you are quite certain this is with kio-extras 23.04? This is a good point... There are two systems, one is more "bleeding edge" and uses the DFS share via VPN link, so I should retest it with 23.04 (because it was recently updated and I didn't retest there since then): # equery b /usr/lib64/qt5/plugins/kf5/kio/smb.so * Searching for /usr/lib64/qt5/plugins/kf5/kio/smb.so ... kde-apps/kio-extras-23.04.0 (/usr/lib64/qt5/plugins/kf5/kio/smb.so) The other system (directly connected to the server LAN segment) has: # equery b /usr/lib64/qt5/plugins/kf5/kio/smb.so * Searching for /usr/lib64/qt5/plugins/kf5/kio/smb.so ... kde-apps/kio-extras-22.12.3 (/usr/lib64/qt5/plugins/kf5/kio/smb.so) That system shows this problem as recently as a few days ago. Do you mean to say that this may have been fixed in 23.04?
> Do you mean to say that this may have been fixed in 23.04? Yes https://invent.kde.org/network/kio-extras/-/commit/46d3f2fd41dece1d49e7295ae986d8e3960e78fb
OTOH, this may also be fixed in Dolphin rather than kio (if there's no way around that behavior): If Dolphin detects 0 bytes free and 0 bytes size at the same time, it should infer that there's no information about free space and just try writing the file. I'm pretty sure it's not kio preventing the write due to this condition (because when launching the terminal from Dolphin, it will put me into a kio mounted directory and I can create files there just fine).
(In reply to Harald Sitter from comment #5) > > Do you mean to say that this may have been fixed in 23.04? > > Yes > https://invent.kde.org/network/kio-extras/-/commit/ > 46d3f2fd41dece1d49e7295ae986d8e3960e78fb Oh wow... Thanks, I'll try. I add this to the patch queue of emerge and reinstall the package. I'm guessing it will apply to 22.12.3 without conflicts. I'll close this if it works for me.
Thanks, it is fixed by your commit. Sorry for not taking more attention to my other system which recently updated to 23.04 - I wasn't really aware of that fact when I wrote the bug report. *** This bug has been marked as a duplicate of bug 431050 ***