As far as I know there is nothing specific built in to protect against that.
I don't think it would be hard to setup regular scans of all your blobs, and keep a log of the latest scan. Then at the next scan, if any of your blob has changed (or blob could not be read), then you know there's a problem. Starting Perkeep with -reindex is already somewhat likely to detect such a problem. On 20 December 2017 at 06:12, Timothy Quinn <[email protected]> wrote: > Advanced file systems like ZFS can protect data against silent corruption > (eg. bitrot). Does Perkeep have similar built in protections against such > silent corruption? > > If it does not contain such bitrot protection at present, would it be > something that can be realistically done in current or roadmapped designs? > > I've been recently burned by bitrot on large compressed VMs that were on a > home NAS which ran Linux mdraid so this is a problem near and dear to me. > > BTW - Wicked project. Keep up the great work! > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
