Error splicing file: No space left on device

qsl

When attempting to transfer a large amount of data (100GB or more) from one hard drive to another at once, I get this error message often (there is a reported sufficient amount of space on the destination drive). I can do the transfer piecemeal, but that means babying it, which isn't time efficient.

The only weirdness I can think of is transferring from the default file system for XFCE to NTFS.

What is going on? How do I mitigate this?

qk4-li3

qsl Before my attempt for humour, I think @brent suggested emptying the trash can.

brent

qk4-li3

for the 10000th time @brent, your eyeglasses, they are on your forehead mate!

brent

qk4-li3 I'm not sure what I glossed over except the 100MB number but I will delete everything I guess

qk4-li3

100 1000 10000 yeah that was the joke mate.

edit. ok, "I'll get my coat…"

brent

qk4-li3 I gotten a lot worse here for being off a single 0, so all good. 😉

still @qsl your observations about transfer over GPT-to-NTFS could very well be right…my only [deleted] suggestion was let grsync do the heavy lifting and make sure the trash cans on both systems were empty.

Harvey

Assuming you are correct that there is free space available, there are a lot of weird bugs with NTFS under Linux so this is probably one of them.

I assume the NTFS drive was connected to Windows at some point. Windows can sometimes leave the drive in a dirty state which can cause odd behaviour. Windows fast startup feature is enabled by default and what it does is prevent the system truely shutting down when you click shutdown in order for the next boot to be faster.

Windows fast startup causes some people who multiboot to have issues with wifi/bluetooth not working in Linux without forcing a hard power off or booting into Windows first then rebooting into Linux. So it is recommended to disable Windows fast boot when multibooting. https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi.html#about-dual-boot-with-windows-and-fast-boot-enabled

My advice is to avoid using NTFS as much as possible in Linux. Many people try share a NTFS drive for their games between Windows and Linux and have nothing but issues which magically go away when they just use a Linux file system for their games when in Linux.

qsl

Harvey Fair enough. Unfortunately being able read/write disks between different OS (event without dual booting) is kinda essential. Still not ready to migrate exclusively to linux and virtual machines aren't ready for prime time in my opinion. Easier just to keep at least one Windows machine around, although I've noticed I don't seem to have this problem using FAT. That might be my go to for transfers.

Alternatively, has anyone had any experiences using something like Disk Genius? As nearly all new data is from the linux machine, maybe I am going about this the wrong way.

BuzzPCSOS

qsl has anyone had any experiences using something like Disk Genius?

That is an interesting option, or you could use the Windows Subsystem for Linux (WSL) to mount EXT4 drives.
I keep an Oracle VirtualBox install of Windows which I run from inside my Linux session. This way I can use Windows for the things that it does best, like working with NTFS drives, while keeping Linux to do all the heavy lifting.
Generally it makes better sense to run Windows from inside Linux than the other way around.

Harvey

FAT will have its own issues. From memory I think FAT32 has a 4GB file size limit. ExFat is probably the better option if you think you'll exceed that limit.

qsl

For those playing along at home, Disk Genius (the free version) is adequate to transfer files from a linux environment to a windows one (although getting windows to boot with an ext4 formatted disk is troublesome).

The problem seemed to be XFCE just really did not like that NTFS partition (reformatted to ext4 and everything is fine).