DCMAKER - 2018-04-26

I wanted to ask over here to cover my bases for this question:

Two parts...first how does bit rot work inside an encrypted container?

If you have a VeraCrypt container in Snapraid. You open a container and do not change any data but while reading data a bit flips. Would this silent coruption be inside the container or on the actual drive itself? As in, does this mean the container would be corrupted or would it be updated thinking the silent corruption was a valid change assuming you have timestamps enabled? Or does the timestamp not update in this case but the container is now a different checksum which would trigger Snapraid flagging the container for an error?

Which case would it be? If it would result in a changed timestamp would the option below work to prevent such a silent corruption?

Okay...i know this is a bit ridiculous but would this theoretically work? Assuming this is very static data (any change would be easily be manually synced without issue)

Snapraid
5 parity
9 data
but inside this I have

9x100GB VeraCrypt containers on each data drive
4 parity
5 data

using a second layer of Snapraid inside the containers to prevent bit rot inside the actual encrypted containers.

Can you run 2 instances of Snapraid on a Computer? or would I have to run Snapraid on my server for the 5x parity/9x data. Then remotely run Snapraid through network (10GbE fiber) from my main desktop running those 9 encrypted containers remotely with Snapraid on my desktop?

I would obiously have to load all 9 containers run sync command on containers first than run sync on server after containers are no longer beign written to.

This would be a giant pain but wouldn't this prevent any chance of bit rot assuming I always sync in the proper order?

https://sourceforge.net/p/snapraid/discussion/1677233/thread/d5e63f94/