Wang Shilong posted on Fri, 21 Feb 2014 10:30:25 +0800 as excerpted:
So my question is, why does scrub show a high (i.e. non-zero) value
for no_csum? I never enabled nodatasum or a similar option.
This should be related to btrfs free space cache, it is designed as
nocow without checksums.
Sebastian Ochmann posted on Wed, 19 Feb 2014 13:58:17 +0100 as excerpted:
So my question is, why does scrub show a high (i.e. non-zero) value for
no_csum? I never enabled nodatasum or a similar option.
I've no answer but have wondered that myself. So hopefully you get an
answer I can read
On 02/20/2014 06:31 PM, Duncan wrote:
Sebastian Ochmann posted on Wed, 19 Feb 2014 13:58:17 +0100 as excerpted:
So my question is, why does scrub show a high (i.e. non-zero) value for
no_csum? I never enabled nodatasum or a similar option.
Did you enable nodatacow option? if nodatacow option
Wang Shilong posted on Thu, 20 Feb 2014 18:51:10 +0800 as excerpted:
On 02/20/2014 06:31 PM, Duncan wrote:
Sebastian Ochmann posted on Wed, 19 Feb 2014 13:58:17 +0100 as
excerpted:
So my question is, why does scrub show a high (i.e. non-zero) value
for no_csum? I never enabled nodatasum or
Hello,
Sebastian Ochmann posted on Wed, 19 Feb 2014 13:58:17 +0100 as excerpted:
So my question is, why does scrub show a high (i.e. non-zero) value for
no_csum? I never enabled nodatasum or a similar option.
Did you enable nodatacow option? if nodatacow option is
On 02/20/2014 07:25 PM, Sebastian Ochmann wrote:
Hello,
Sebastian Ochmann posted on Wed, 19 Feb 2014 13:58:17 +0100 as
excerpted:
So my question is, why does scrub show a high (i.e. non-zero)
value for
no_csum? I never enabled nodatasum or a similar option.
Did you
Hello everyone,
I have a question: What exactly does the value for no_csum mean when
doing a scrub with the -R option? Example output:
sudo btrfs scrub start -BR /
scrub done for ...
...
csum_errors: 0
verify_errors: 0
no_csum: 70517
csum_discards: 87381
super_errors: 0
...
