From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub status misreports as "interrupted"
Date: Tue, 09 Dec 2014 14:16:42 +0200 [thread overview]
Message-ID: <5486E82A.6080301@gmail.com> (raw)
In-Reply-To: <20141122131318.05609d5f@marcec.fritz.box>
I've got the exact same problem, with a 4 drive RAID1. kernel 3.18-git
and btrfs tools-git, all built yesterday.
On 22/11/2014 2:13 μμ, Marc Joliet wrote:
> Hi all,
>
> While I haven't gotten any "scrub already running" type errors any more, I do
> get one strange case of state misreport. When running scrub on /home (btrfs
> RAID10), after 3 of 4 drives have completed, the 4th drive (sdb) will report as
> interrupted, despite still running:
>
> # btrfs scrub status -d /home
> scrub status for 472c9290-3ff2-4096-9c47-0612d3a52cef
> scrub device /dev/sda (id 1) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3380 seconds
> total bytes scrubbed: 252.86GiB with 0 errors
> scrub device /dev/sdb (id 2) status
> scrub started at Sat Nov 22 11:57:34 2014, interrupted after 3698 seconds, not running
> total bytes scrubbed: 217.50GiB with 0 errors
> scrub device /dev/sdc (id 3) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3013 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
> scrub device /dev/sdd (id 4) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 2994 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
>
> The funny thing is, the time will still update as the scrub keeps going:
>
> # btrfs scrub status -d /home
> scrub status for 472c9290-3ff2-4096-9c47-0612d3a52cef
> scrub device /dev/sda (id 1) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3380 seconds
> total bytes scrubbed: 252.86GiB with 0 errors
> scrub device /dev/sdb (id 2) status
> scrub started at Sat Nov 22 11:57:34 2014, interrupted after 4136 seconds, not running
> ^^^^^^^^^^^^
> total bytes scrubbed: 239.44GiB with 0 errors
> scrub device /dev/sdc (id 3) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3013 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
> scrub device /dev/sdd (id 4) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 2994 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
>
> This has happened a few times, and when sdb finally finishes, the status is then
> reported correctly as "finished":
>
> # btrfs scrub status -d /home
> scrub status for 472c9290-3ff2-4096-9c47-0612d3a52cef
> scrub device /dev/sda (id 1) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3380 seconds
> total bytes scrubbed: 252.86GiB with 0 errors
> scrub device /dev/sdb (id 2) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 4426 seconds
> total bytes scrubbed: 252.88GiB with 0 errors
> scrub device /dev/sdc (id 3) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 3013 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
> scrub device /dev/sdd (id 4) history
> scrub started at Sat Nov 22 11:57:34 2014 and finished after 2994 seconds
> total bytes scrubbed: 252.85GiB with 0 errors
>
> Kernel and btrfs-progs version:
>
> # uname -a
> Linux marcec 3.16.7-gentoo #1 SMP PREEMPT Fri Oct 31 22:45:54 CET 2014 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
>
> # btrfs --version
> Btrfs v3.17.1
>
> Should I open a report on bugzilla?
>
next prev parent reply other threads:[~2014-12-09 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 12:13 btrfs scrub status misreports as "interrupted" Marc Joliet
2014-12-09 12:16 ` Konstantinos Skarlatos [this message]
2014-12-10 2:51 ` Anand Jain
2014-12-10 19:28 ` Marc Joliet
2014-12-10 19:32 ` Konstantinos Skarlatos
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=5486E82A.6080301@gmail.com \
--to=k.skarlatos@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.