this post was submitted on 21 Feb 2024
13 points (88.2% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55303 readers
719 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Since I'm not too familiar with your environment I'm just going to list some possibilities.
Check that you're not using a fat16/fat32 filesystem anywhere. Host, Docker, download location. If this is the cause, exfat is supported by Windows and Linux if you need reverse compatibility.
Confirm you're running the 64bit version.
Can you determine if the problem starts happening around the 4GB size.
Perhaps there's not enough free space for it to download and copy the file from the temporary location to the destination at the same time.
Perhaps the file name including the path has become too long.
Ah I guess you are right I was saving everything to an internal 500 gb drive in the laptop and then transferring over to a raid but if I just download said files to the raid they seem to be going fine. Guess I should wipe that internal drive and try to make it compatible.
Also is it a problem that my os (Ubuntu server) appears to be on the same fat 32 format?
If you're not concerned with compatibility with Windows. Replace your filesystem with ext4.
Yeah, fat32 is the devil when it comes to working with large files. (It's fine for /boot)