From: Sandy McArthur Jr <sandymac@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: What does scrub tell me?
Date: Wed, 4 Feb 2015 12:31:07 -0500 [thread overview]
Message-ID: <CAPs0Big=8SsBRFjrDPcradYW100GUnWEzC=ycvvDQScTSYKt5A@mail.gmail.com> (raw)
Does a btrfs scrub verify the integrity of the whole filesystem or
just the data in that filesystem?
I recently removed some unreliable drives from my multi-volume RAID1
btrfs filesystem and ran a scrub that completed with two corrected
errors (see below). I've struggled with this filesystem due to poor
choices in hardware on my part and had to recover it several times. As
of now I've eliminated all older drives or drives labeled as "desktop"
drives. (Knowing what I know now, I'm impressed with how well btrfs
has preserved my data despite myself.)
I'm at a point where I can grow my existing btrfs filesystem as RAID1
or I can afford to migrate data to a new btrfs single filesystem and
then add drives back in to get back to RAID1 mirroring again. Is there
value to starting a fresh btrfs filesystem given my history?
# btrfs scrub status /mcmedia/ ; echo ; btrfs --version
scrub status for 94b3345e-2589-423c-a228-d569bf94ab58
scrub resumed at Mon Feb 2 22:03:14 2015 and finished after 204126 seconds
total bytes scrubbed: 23.38TiB with 2 errors
error details: csum=2
corrected errors: 2, uncorrectable errors: 0, unverified errors: 0
Btrfs v3.18.2
Both errors were from: [/dev/sdm1].corruption_errs 2
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
next reply other threads:[~2015-02-04 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:31 Sandy McArthur Jr [this message]
2015-02-05 3:43 ` What does scrub tell me? Duncan
2015-02-05 5:16 ` Qu Wenruo
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='CAPs0Big=8SsBRFjrDPcradYW100GUnWEzC=ycvvDQScTSYKt5A@mail.gmail.com' \
--to=sandymac@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).