From: Forza <forza@tnonline.net>
To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: question to btrfs scrub
Date: Thu, 29 Jun 2023 11:12:54 +0200 [thread overview]
Message-ID: <d875533b-1607-2c4c-45be-44edd6a38eba@tnonline.net> (raw)
In-Reply-To: <PR3PR04MB734055F52AB54D94193FA79CD625A@PR3PR04MB7340.eurprd04.prod.outlook.com>
On 2023-06-29 10:26, Bernd Lentes wrote:
> Hi guys,
>
> i have a BTRFS volume which produces a lot of errors in the syslog.
> Here I got the recommendation to start a “btrfs scrub” on that volume.
> I made an image of that volume (with dd) and started the scrub on that.
> That’s the result:
>
> ha-idg-1:/mnt/sdc1/ha-idg-1/image # btrfs scrub start -B /mnt/image/
>
> scrub done for bbcfa007-fb2b-432a-b513-207d5df35a2a
> Scrub started: Tue Jun 27 20:47:26 2023
> Status: finished
> Duration: 35:39:48
> Total to scrub: 5.07TiB
> Rate: 40.16MiB/s
> Error summary: csum=1052
> Corrected: 0
> Uncorrectable: 1052
> Unverified: 0
> ERROR: there are uncorrectable errors
>
> 1052 checksum errors on a 5TB volume. Is that much, or is that normal ?
> What can I do ?
> Start a btrfs check ? First on the image before on the original ?
>
Uncorrectable errors means there were some corruptions that Btrfs could
not correct using a good copy (RAID/DUP profiles). Those corruptions
could be different things, for example media errors on the disk drive.
Is it just a single disk that you have in this filesystem?
What does smartctl -x /dev/xxx show? Especially look at the table
containing Uncorrectable_Error_Cnt or Reallocated_Sector_Ct.
You can also issue a drive self-test using `smartctl -t long /dev/xxx`
~F
prev parent reply other threads:[~2023-06-29 9:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 8:26 question to btrfs scrub Bernd Lentes
2023-06-29 9:08 ` Qu Wenruo
2023-06-30 9:59 ` Bernd Lentes
2023-06-30 10:16 ` Qu Wenruo
2023-07-04 16:03 ` Bernd Lentes
2023-07-04 17:00 ` Bernd Lentes
2023-07-04 22:19 ` Qu Wenruo
2023-07-05 8:39 ` Bernd Lentes
2023-07-05 8:45 ` Qu Wenruo
2023-07-05 15:01 ` Bernd Lentes
2023-07-05 17:53 ` Remi Gauvin
2023-07-06 6:23 ` Qu Wenruo
2023-07-06 13:18 ` Remi Gauvin
2023-07-07 21:02 ` Bernd Lentes
2023-07-07 20:54 ` Bernd Lentes
2023-07-08 5:08 ` Qu Wenruo
2023-07-18 15:34 ` Bernd Lentes
2023-07-07 20:40 ` Bernd Lentes
2023-07-06 6:19 ` Qu Wenruo
2023-07-06 7:04 ` Andrei Borzenkov
2023-07-06 7:07 ` Qu Wenruo
2023-07-07 20:48 ` Bernd Lentes
2023-07-07 22:17 ` Qu Wenruo
2023-06-29 9:12 ` Forza [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d875533b-1607-2c4c-45be-44edd6a38eba@tnonline.net \
--to=forza@tnonline.net \
--cc=bernd.lentes@helmholtz-muenchen.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox