This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
for a non-home share which is largely static should checksums be turned on (bitrot)
Rebuilding a Pro 6 running 6.6.0 with 3GB of memory and stock processor
I assume that turning on bit rot protection (CoW) is a reasonable thing to do.
I also assume that it is transparent to the end user (i.e. compares of actual file sizes and checksums for the files are unchanged as it lives in OS based metadata and is not part of things like backups)
I am running a 6 drive Xraid2 with single redundancy
I assume that turning on bit rot protection (CoW) is a reasonable thing to do.
It is transparent to the end user - unless it finds a corrupted file that it can't repair. In that case it won't allow you to access the file.
My advice is to turn it on for shares that have snapshots enabled. If a share isn't suitable for snapshots (one example is a torrent download folder), then I'd leave it off.
I assume that turning on bit rot protection (CoW) is a reasonable thing to do.
It is transparent to the end user - unless it finds a corrupted file that it can't repair. In that case it won't allow you to access the file.
My advice is to turn it on for shares that have snapshots enabled. If a share isn't suitable for snapshots (one example is a torrent download folder), then I'd leave it off.
