"Error splicing file: File too large"

[Karl Auer]

On Sat, 2016-09-17 at 15:23 -0700, Dave Stevens wrote:
> I made a zip file of 14.1 GB and copied it to a new 16GB usb flash  
> drive and got this message at about the 99% mark. I didn't know
> there was a file size limit and the drive properties showed enough
> space beforehand.

There is no file size limit at 14.1GB.

That 16GB of capacity includes everything - including losses to
formatting and file system chunking. Also, stick sizes are often in
billions of bytes, not actual gigabytes - there's a significant
difference when you get up into high numbers.

Sometimes cheap USB sticks are also deliberately mislabeled and
sometimes even fraudulently programmed to report higher capacities than
they have.

But I don't think any of that is your problem:

> 2GB RAM, lots of space on /dev/sda1, /dev/sdb1 (the flash drive) is  
> FAT32, is that an issue?

My understanding is that FAT32 has a maximum file size of 4GB. This
website seems to confirm that:

 https://technet.microsoft.com/en-us/library/cc938432.aspx

I don't know how you got to 99%.

To store files larger than 4GB, you will need to use NTFS or one of the
Unix filesystem types such as ext4. This wikipedia page has a good
comparison of filesystem limits:

https://en.wikipedia.org/wiki/Comparison_of_file_systems

NTFS is pretty much the only choice if you need to share between Win
and random nonWin systems, but it is a very sensitive filesystem;
always properly eject it before removal.

ext4 is much more robust, and with third-party software you can still
read it on Windows:

   http://www.diskinternals.com/linux-reader/

However, I'm not sure it can read encrypted partitions.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B
Old fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4