Any missing files that fit the heuristic should be tried with zero-filled files when "Verify local data" is run before actually reporting them as missing.This is the point where an option might be in order ("Remove padding files from downloads") for everything else I wouldn't see any reason to add user configuration.Files that fit the padding heuristic and are zero-filled could be removed when the download is completed (or never be put to disk in the first place).Files filled with zeroes can be stored as sparse files where the file system supports it, thus not taking up actual disk space. ![]() ![]() (There's some room for optimization in evicting the zeroed blocks first, but it's probably corner case enough not to matter). In the exotic case that a file is named like padding but isn't actually, verification will fail, and those blocks need to be actually downloaded.
0 Comments
Leave a Reply. |