On Mon, Jul 21, 2014 at 10:53 AM, Warren Young <war...@etr-usa.com> wrote:
> On 7/20/2014 23:39, Gour wrote: > >> >> but I wonder how safe is to operate Fossil repo with checksum checking >> off? >> > > > If you're running Fossil on a system that already does data checksumming > (not just *metadata* checksumming) I can't see that this feature of Fossil > buys you anything. So, ZFS, ReFS, btrfs... > It could catch bugs in Fossil that cause malformed check-ins to be generated. I would say that as long as you are running a version of Fossil that is well-tested, it is safe to leave repo checksumming turned off. The self-hosting Fossil repo (and the SQLite repo) both tend to run the latest tip of trunk of Fossil and the tip of trunk could, potentially, have bugs in its check-in logic. So I'll just keep repo checksumming turned on for those repos, thank you. But if you are running a release version of Fossil, I think it is entirely reasonable to turn repo checksumming off if you would otherwise have a performance problem. The repo checksum mechanism has found bugs in the past - for example trying to "fossil add" a symbolic link or a unix special file. I suppose the repo checksum might also find the problem of trying to do a check-in while the files in the checkout are simultaneously being changed by another process. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
