The problem occurs when using flexbackup with the afio back end. afio tries very hard to produce archives that are cpio compatible. However, if a file being backed up exceeds the size that cpio can handle (2GiB), afio warns of the potential issue, uses an extended (but non-cpio-compatible) file header that can handle the larger size, completes the backup successfully, and returns a non-zero result code. flexbackup currently treats this result code as a hard error and marks the backup as failed. There's an afio command line option to suppress this warning (and the resultant non-zero result code). Since flexbackup can also use cpio as a back end, it seems reasonable to assume that those who want cpio-compatible archives should use cpio as the back end. Patch coming. - John
Created attachment 129271 [details, diff] Patch applies afio large file fix. This patch adds a command line option to the invocation of afio that allows it to silently produce afio extended format archives if the incoming file size warrants. - John
Took your fix from Sunrise...thanks a lot.
