Walter Tuppa

no, since the bad block marking is inivisble to the interface to the host.

use the -p option of scrub, takes either a percentage or the string "new".

try ionice, not nice since I/O is the problem.

PAM can limit size of a single file (and many more things). ulimit -a will show some limits of your process.

i can tell you the 8.7TB (or 8.7*10e12): that is 8 * 1024 * 1024 * 1024 * 1024= 879609302208 Bytes or 8TiB (or signed 32bit times 4KB sector size). that is exactly the size of your first parity file. one small letter can make really a difference. good thing, that it is working. I had the idea, because if you use split parity at a time and later on get a large disc, you may copy both split parity files to the big disc and this works.

i can tell you the 8.7TB (or 8.710e12): that is 8102410241024*1024= 879609302208 Bytes or 8TiB (or signed 32bit times 4KB sector size). that is exactly the size of your first parity file. one small letter can make really a difference. good thing, that it is working. I had the idea, because if you use split parity at a time and later on get a large disc, you may copy both split parity files to the big disc and this works.

Maybe you can use split parity with two parity files on same disc. Never tried, but it may work.

maybe you can ignore them in the array. SnapRAID has an option to ignore directories or files (probably an own directory for always changing files would be the best) in its configuration file.