From: Sandy McArthur Jr <sandymac@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs scrub status reports not running when it is
Date: Wed, 14 Jan 2015 16:26:00 -0500 [thread overview]
Message-ID: <CAPs0Bij=86RtrvY3MApgxKvUdKe0xanpysguo5quWJCBfGEE3w@mail.gmail.com> (raw)
In-Reply-To: <CAPs0BijZX-BcM7uRq58TwSUqsNRqsySXeHYRezgVQcfXw-d22g@mail.gmail.com>
Okay, different output when the scrub is actually complete:
completed status:
scrub status for 94b3345e-2589-423c-a228-d569bf94ab58
scrub started at Tue Jan 13 01:18:22 2015 and finished after 139459 seconds
total bytes scrubbed: 23.30TiB with 513 errors
error details: verify=19 csum=494
corrected errors: 512, uncorrectable errors: 1, unverified errors: 0
Still, the output when wrapping up is still not intuitive to me:
"scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136982
seconds, not running"
On Wed, Jan 14, 2015 at 4:06 PM, Sandy McArthur Jr <sandymac@gmail.com> wrote:
> Sometimes btrfs scrub status reports that is not running when it still is.
>
> I think this a cosmetic bug. And I believe this is related to the
> scrub completing on some drives before others in a multi-drive btrfs
> filesystem that is not well balanced.
>
> Based on `iostat 1` activity the last drive in the btrfs filesystem
> was still being scrubbed at the time I copied the output below, you
> can see the total bytes scrubbed is increasing despite showing as "not
> running". The last drive being scrubbed was not the device identified
> when you list mount points with `mount`:
>
>
> # date ; echo ; btrfs scrub status /mcmedia/
> Wed Jan 14 15:20:18 EST 2015
>
> scrub status for 94b3345e-2589-423c-a228-d569bf94ab58
> scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136912
> seconds, not running
> total bytes scrubbed: 23.05TiB with 513 errors
> error details: verify=19 csum=494
> corrected errors: 512, uncorrectable errors: 1, unverified errors: 0
>
>
> # date ; echo ; btrfs scrub status /mcmedia/
> Wed Jan 14 15:21:25 EST 2015
>
> scrub status for 94b3345e-2589-423c-a228-d569bf94ab58
> scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136982
> seconds, not running
> total bytes scrubbed: 23.06TiB with 513 errors
> error details: verify=19 csum=494
> corrected errors: 512, uncorrectable errors: 1, unverified errors: 0
>
>
> # uname -a
> Linux mcplex 3.18.2-gentoo #1 SMP Mon Jan 12 10:24:25 EST 2015 x86_64
> Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz GenuineIntel GNU/Linux
>
> # btrfs --version
> Btrfs v3.18.1
>
>
> --
> Sandy McArthur Jr
>
> "He who dares not offend cannot be honest."
> - Thomas Paine
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
next prev parent reply other threads:[~2015-01-14 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 21:06 btrfs scrub status reports not running when it is Sandy McArthur Jr
2015-01-14 21:23 ` Marc Joliet
2015-01-14 21:26 ` Sandy McArthur Jr [this message]
2015-01-14 22:27 ` Zach Brown
2015-01-15 11:24 ` David Sterba
2015-01-15 18:02 ` Zach Brown
2015-01-19 17:45 ` David Sterba
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='CAPs0Bij=86RtrvY3MApgxKvUdKe0xanpysguo5quWJCBfGEE3w@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).