check_btrfs_errors exited with return code 64

  • Hello,
    is the second day that i receive an email from Anacron job 'cron.daily


    /etc/cron.daily/openmediavault-check_btrfs_errors:
    Performing an error check on Btrfs file systems.
    Checking file system /dev/md0 for errors ...
    run-parts: /etc/cron.daily/openmediavault-check_btrfs_errors exited with return code 64
    /etc/cron.daily/openmediavault-check_locked_users:
    Checking for locked/banned users.
    INFO: No locked/banned users found.
    /etc/cron.daily/openmediavault-check_ssl_cert_expiry:
    Perform a check for expired SSL certificates.
    /etc/cron.daily/openmediavault-pending_config_changes:
    Checking for pending configuration changes.



    I searched on google about this kind of error, but with not result, what means exit code 64?
    on the /dev/md0 disk I have BTFRS file system installed on 3 disk with RAID5..is the file system ok?

    what ssl certified is expired, not sure to have one? or the text is just saying that is doing a check, not necessarily that there is an expired certified (is a little bit confusing)


    note, two days ago, I also updated OMV6 with:


    Preparing to unpack .../containerd.io_1.6.19-1_amd64.deb ...

    Unpacking containerd.io (1.6.19-1) over (1.6.18-1) ...

    Preparing to unpack .../openmediavault_6.3.5-2_all.deb ...

    Unpacking openmediavault (6.3.5-2) over (6.3.4-1) ...

    Setting up openmediavault (6.3.5-2) ...

    Installing new version of config file /etc/cron.daily/openmediavault-check_locked_users ...

    Installing new version of config file /etc/cron.daily/openmediavault-check_ssl_cert_expiry ...

    Installing new version of config file /etc/cron.daily/openmediavault-cron-apt ...

    Installing new version of config file /etc/cron.daily/openmediavault-flush-mailq ...

    Installing new version of config file /etc/cron.daily/openmediavault-mdadm ...

    Installing new version of config file /etc/cron.daily/openmediavault-pending_config_changes ...

    Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ...


    thank you for any help!

    • Official Post

    From here:

    btrfs-device(8) — BTRFS documentation

    Quote

    -c|--check


    Check if the stats are all zeros and return 0 if it is so. Set bit 6 of the return code if any of the statistics is no-zero. The error values is 65 if reading stats from at least one device failed, otherwise it’s 64.

    Use the linked documentation and


    btrfs device stats <mountpoint>


    to get more info.

  • thank you for the help :) ,
    I'm a beginner and I'm trying to understand your post.
    so from what I understood all the devices reply (otherwise I get exit code 65), but not all the stats are 0. correct?

    I launched through the shell the btrfs device stats /dev/md0 command, and I get:

    [/dev/md0].write_io_errs 0

    [/dev/md0].read_io_errs 0

    [/dev/md0].flush_io_errs 0

    [/dev/md0].corruption_errs 144

    [/dev/md0].generation_errs 0

    so, seems I have a problem.. how much is bad? what I have to do?
    the filesystem is on 3 WD Red 3Tbyte with Raid5.
    thank you for any help!

  • votdev

    Added the Label OMV 6.x
  • Do you regularly run a scrub? If not, run a scrub and post the output.


    If it corrects the 144 errors, reset the counters.

    I made for the first time a scrub (I didn't know nothing about it || :D )

    btrfs scrub start /dev/md0

    at the end appeared this:

    root@openmediavault:~# WARNING: errors detected during scrubbing, corrected


    After I executed this:

    btrfs scrub status /dev/md0

    appeared this:

    UUID: 05508cd1-200e-452f-9800-644e763821d2

    Scrub started: Tue Mar 28 11:00:41 2023

    Status: finished

    Duration: 6:28:02

    Total to scrub: 2.39TiB

    Rate: 107.76MiB/s

    Error summary: no errors found


    Is correct that no errors were found? or maybe means that at the end of the scrub all the errors are corrected?

    I executed again also this:

    btrfs device stats /dev/md0

    and the output is the same of before, with the 144 errors

    [/dev/md0].write_io_errs 0

    [/dev/md0].read_io_errs 0

    [/dev/md0].flush_io_errs 0

    [/dev/md0].corruption_errs 144

    [/dev/md0].generation_errs 0


    so I'm confused, is ok that there are still the 144 errors? or is normal, and when you talk about reset the counters you are talking about reset this corruption_errs variable?


    thank you for your patience

    • Official Post

    root@openmediavault:~# WARNING: errors detected during scrubbing, corrected

    Looks good.



    [/dev/md0].corruption_errs 144

    These are accumulated errors. You need to reset the counter after they have been corrected with scrub.

    For this use -z option

    btrfs-device(8) — BTRFS documentation

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!