OS/ File system repair of a large image file (such as fossil's) is the way ahead?
I say that because I would imagine it better implemented as a fossil background activity communicating with a replica elsewhere. Sent from my iPhone > On Jun 28, 2016, at 8:30 AM, Karel Gardas <gard...@gmail.com> wrote: > > You need to use something like RAID1 setup with N drives using either > ZFS or btrfs. If you are on dragonfly bsd probably hammer does that > too. Also backup and scrub your disk array quite often... > > Ah, just found out that zfs/btrfs is also cited by the article so you > already know that... > >> On Tue, Jun 28, 2016 at 1:09 PM, Paul Hammant <p...@hammant.org> wrote: >> Bitrot - >> http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/ >> - data in SSD or HD being corrupted by (say) nutrinos over time. See also a >> guy/gal lamenting their corrupted photo collection - >> https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/ >> >> Anyway, will two fossil installs replicating each other do anything with >> merkle trees to heal such bitrot silently and in the background? >> >> - Paul >> >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
