Description:
When attempting to copy a file into the local Internxt Drive folder on Fedora Linux using a GUI file manager (KDE Dolphin), the operating system throws a "not enough space on the disk" error.
Troubleshooting confirms that the physical disk has plenty of space. The core issue is that the FUSE mount created by the Internxt client is reporting exactly 0 bytes total size and 0 bytes available to the OS. Because Dolphin performs a pre-flight space check before copying, it immediately blocks any file transfers. However, terminal commands (like cp) bypass this check and succeed.
The Internxt App GUI itself does not show any errors or issues.
Steps to Reproduce:
- Install and log into the Internxt Linux client on Fedora (KDE Plasma).
- Wait for the
~/Internxt Drive folder to mount via FUSE.
- Attempt to copy any file into the directory using the KDE Dolphin file manager.
- Observe the OS error:
There is not enough space on the disk to write file:///...
- Attempt to copy the exact same file using the terminal (
cp file.zip "/home/$USER/Internxt Drive/"). Observe that it succeeds.
- Run
df -h "/home/$USER/Internxt Drive/" and observe that the virtual drive reports 0 space.
Expected Behavior:
The FUSE mount should report the actual available cloud storage quota to the operating system (e.g., 20G), or at least a sufficiently large dummy value. This is necessary so that GUI file managers like KDE Dolphin do not block files during their pre-transfer space checks.
Actual Behavior:
The FUSE mount reports 0 size and 0 available, causing strict GUI file managers to immediately reject local file copies.
$ df -h "/home/user/Internxt Drive"
Filesystem Size Used Avail Use% Mounted on
/dev/fuse 0 0 0 - /home/user/Internxt Drive
$ findmnt "/home/user/Internxt Drive"
Description:
When attempting to copy a file into the local Internxt Drive folder on Fedora Linux using a GUI file manager (KDE Dolphin), the operating system throws a "not enough space on the disk" error.
Troubleshooting confirms that the physical disk has plenty of space. The core issue is that the FUSE mount created by the Internxt client is reporting exactly
0bytes total size and0bytes available to the OS. Because Dolphin performs a pre-flight space check before copying, it immediately blocks any file transfers. However, terminal commands (likecp) bypass this check and succeed.The Internxt App GUI itself does not show any errors or issues.
Steps to Reproduce:
~/Internxt Drivefolder to mount via FUSE.There is not enough space on the disk to write file:///...cp file.zip "/home/$USER/Internxt Drive/"). Observe that it succeeds.df -h "/home/$USER/Internxt Drive/"and observe that the virtual drive reports0space.Expected Behavior:
The FUSE mount should report the actual available cloud storage quota to the operating system (e.g., 20G), or at least a sufficiently large dummy value. This is necessary so that GUI file managers like KDE Dolphin do not block files during their pre-transfer space checks.
Actual Behavior:
The FUSE mount reports
0size and0available, causing strict GUI file managers to immediately reject local file copies.