Jamie Lokier wrote:
Daniel Carrera wrote:
But there is no way to distinguish between file corruption and a
legitimate change. All you can do is keep old backups for a few days or
weeks and hope that you detect the file corruption before the backup
rotation deletes all the good copies.
I'm under the impression ZFS (Solaris) and BTRFS (Linux) allow a
checksum to be stored with the file data, so if the data changes due
to disk corruption or glitches in the I/O cabling, that will be detected.
Thinking a little more about this problem, there is one possible
solution: Store a checksum and mod time when the file is backed up. If
later on, the file's checksum is different but the modification time has
not changed, it is safe to assume that the file is corrupt. So we can
distinguish between legitimate edits an accidental corruption.
Daniel.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
