* btrfs scrub status misreports as "interrupted"
@ 2014-11-22 12:13 Marc Joliet
2014-12-09 12:16 ` Konstantinos Skarlatos
0 siblings, 1 reply; 5+ messages in thread
From: Marc Joliet @ 2014-11-22 12:13 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 3157 bytes --]
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?
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs scrub status misreports as "interrupted"
2014-11-22 12:13 btrfs scrub status misreports as "interrupted" Marc Joliet
@ 2014-12-09 12:16 ` Konstantinos Skarlatos
2014-12-10 2:51 ` Anand Jain
0 siblings, 1 reply; 5+ messages in thread
From: Konstantinos Skarlatos @ 2014-12-09 12:16 UTC (permalink / raw)
To: linux-btrfs
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?
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs scrub status misreports as "interrupted"
2014-12-09 12:16 ` Konstantinos Skarlatos
@ 2014-12-10 2:51 ` Anand Jain
2014-12-10 19:28 ` Marc Joliet
0 siblings, 1 reply; 5+ messages in thread
From: Anand Jain @ 2014-12-10 2:51 UTC (permalink / raw)
To: Konstantinos Skarlatos; +Cc: linux-btrfs
Is there any relevant log in the dmegs ?
On 09/12/2014 20:16, Konstantinos Skarlatos wrote:
> 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?
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-12-10 19:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-22 12:13 btrfs scrub status misreports as "interrupted" Marc Joliet
2014-12-09 12:16 ` Konstantinos Skarlatos
2014-12-10 2:51 ` Anand Jain
2014-12-10 19:28 ` Marc Joliet
2014-12-10 19:32 ` Konstantinos Skarlatos
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).