![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 10/7/22 18:01, Lew Wolfgang wrote:
I'm thinking a fancy shell script is called for here. I bet that rsync should be leveraged to allow restarting from an aborted copy process.
Any ideas? It seems to be a common requirement, maybe someone's done it already?
Well... That really depends on what is in the files. If they are binary, then you are going to need to split on a record boundary if you hope to mount some arbitrary JBOD copy somewhere and read something other than gibberish. If they are text, that's a bit easier, but the storage would be less than optimal from a size standpoint. There is a coreutils utility called 'split' that allows you to slice large files into smaller files by lines or bytes and it also has a --filter=command option to filter through a shell script which would give you the ability to umount/mount new JBOD devices between parts of the original being written. There are no limits listed in the man page (man 1 split), but I suspect a 64-bit size is likely the upper-limit (more than enough for your needs). I haven't tried on large multi-gig files, but no reason it would work any differently than on smaller files. -- David C. Rankin, J.D.,P.E.