You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just as a note #2628 resulting in disabling sparse files because of an unrar issue testing passwords for encrypted files, I think that part is fixable, but it would require more tarfile changes.
I think @thezoggy raised a good point about having a switch to disable sparse files; there could be some non-standard setups where a directory is a network mount or something and I'm not sure how it would cope with truncate/sparse calls.
Strictly speaking the sparse file part isn't required to fill in the gaps of missing articles since the more important change was writing articles at the correct offsets.
For SAB the main benefit of sparse files would be if there are lots of missing articles because keeping failed downloads wouldn't take up so much space, i.e. several 100MB files but we only had the last 1MB article, would mean disk allocation of ~1MB.
Rather than just being able to add more servers and retry failures I have a pipe dream of being able to take two .nzb files pointing to different uploads and SAB being able to merge them and fille the gaps with different articles because it can tell that some/all files are the same.
I'm not sure how effective it would be though if upload split sizes vary a lot.
Description
Since we now have the option to write sparse-files, we should implement really article-level retries.
The text was updated successfully, but these errors were encountered: