Hi Guillermo,
I agree. BackupPC's RefCnt/Fsck is a must IMHO.
A main difference between PoolNightlyDigestCheck and btrfs' builtin
checksumming is that the nightly digest checks proactively scan the data and
will tell you about broken files as soon as they break (well, as soon as the
next check
>
> One ensures against file system bit rot, the other ensures backup file
> consistency.
>
I would say $Conf{PoolNightlyDigestCheckPercent} = 1 is also a check for
bit rot, as the only thing it does is to read the file, re-calculate the
md5 checksum, and compares it with its name (which is the md
On 2021-05-04 00:45, Ghislain Adnet wrote:
No, because that's like turning off the airbags on your car because
you already have seatbelts.
thanks for your answer, i am trying to understand more about this.
If this check is to prevent bitrot or disk corruption of an existing
file, and if rsy
No, because that's like turning off the airbags on your car because you already
have seatbelts.
thanks for your answer, i am trying to understand more about this.
If this check is to prevent bitrot or disk corruption of an existing file, and
if rsync is sure the file is ok, and then that Z
On 2021-04-30 00:09, Ghislain Adnet wrote:
hi,
Should this setting put to 0 on ZFS or BTRFS as the filesystem
allready do checksumming and will detect issues ?
No, because that's like turning off the airbags on your car because you
already have seatbelts.
hi,
Should this setting put to 0 on ZFS or BTRFS as the filesystem allready do
checksumming and will detect issues ?
Or is it something différent ?
$Conf{PoolNightlyDigestCheckPercent} = 1;
Integrity check the pool files by confirming the md5 digest of the contents
matches their file
