From: Su Yue <Damenly_Su@gmx.com>
To: Andrew Pam <andrew@sericyb.com.au>
Cc: Graham Cobb <g.btrfs@cobb.uk.net>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs reports nonsense scrub status
Date: Sat, 09 May 2020 16:02:31 +0800 [thread overview]
Message-ID: <mu6h7cyw.fsf@gmx.com> (raw)
In-Reply-To: <ace72f18-724c-9f2c-082f-cb478b8a63ef@sericyb.com.au>
On Sat 09 May 2020 at 01:06, Andrew Pam <andrew@sericyb.com.au>
wrote:
> And here we are again:
>
> $ sudo btrfs scrub status -d /home UUID:
> 85069ce9-be06-4c92-b8c1-8a0f685e43c6 scrub device /dev/sda (id
> 1) status Scrub resumed: Sat May 9 02:52:12 2020 Status:
> running Duration: 7:02:55 Time left:
> 32261372:31:39 ETA: Fri Sep 17 23:35:41 5700 Total
> to scrub: 3.66TiB Bytes scrubbed: 3.67TiB Rate:
> 151.47MiB/s Error summary: no errors found scrub device
> /dev/sdb (id 2) status Scrub resumed: Sat May 9 02:52:12
> 2020 Status: running Duration: 7:02:59 Time
> left: 31973655:40:34 ETA: Mon Nov 21
> 19:44:36 5667 Total to scrub: 3.66TiB Bytes scrubbed:
> 3.70TiB Rate: 152.83MiB/s Error summary: no
> errors found
>
Weird. Any operation was done since the last "interrupted" status?
Does iotop show any actual io of the two devices?
--
Su
> I tried building btrfs-progs v5.6.1 from source, but it gives exactly
> the same results.
>
> Cheers,
> Andrew
next prev parent reply other threads:[~2020-05-09 8:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 5:46 btrfs-progs reports nonsense scrub status Andrew Pam
2020-05-05 9:51 ` Graham Cobb
2020-05-05 10:10 ` Andrew Pam
2020-05-05 20:39 ` Andrew Pam
2020-05-06 23:42 ` Chris Murphy
2020-05-07 1:09 ` Andrew Pam
2020-05-07 5:10 ` Chris Murphy
2020-05-07 5:36 ` Chris Murphy
2020-05-07 5:56 ` Andrew Pam
2020-05-08 2:26 ` Chris Murphy
2020-05-08 2:31 ` Andrew Pam
2020-05-08 2:48 ` Chris Murphy
2020-05-08 2:54 ` Andrew Pam
2020-05-08 3:55 ` Chris Murphy
2020-05-08 4:04 ` Andrew Pam
2020-05-08 4:21 ` Chris Murphy
2020-05-08 4:42 ` Andrew Pam
2020-05-08 4:45 ` Chris Murphy
2020-05-08 4:52 ` Andrew Pam
2020-05-08 7:37 ` Chris Murphy
2020-05-08 8:19 ` Andrew Pam
2020-05-08 11:21 ` Graham Cobb
2020-05-08 12:54 ` Andrew Pam
2020-05-08 17:06 ` Andrew Pam
2020-05-08 21:20 ` Chris Murphy
2020-05-08 21:31 ` Chris Murphy
2020-05-09 10:15 ` Andrew Pam
2020-05-09 20:33 ` Chris Murphy
2020-05-10 1:14 ` Chris Murphy
2020-05-10 1:28 ` Andrew Pam
2020-05-10 1:32 ` Andrew Pam
2020-05-10 11:52 ` Graham Cobb
2020-05-10 17:21 ` Graham Cobb
2020-05-10 17:27 ` Andrew Pam
2020-05-10 1:30 ` Andrew Pam
2020-05-10 6:17 ` Andrew Pam
2020-05-11 1:39 ` Andrew Pam
2020-05-11 4:46 ` Chris Murphy
2020-05-13 6:47 ` Andrew Pam
2020-05-14 0:13 ` Chris Murphy
2020-05-14 16:18 ` Graham Cobb
2020-05-15 2:37 ` Andrew Pam
2020-05-15 11:27 ` Graham Cobb
2020-07-04 14:51 ` Andrew Pam
2020-05-09 8:02 ` Su Yue [this message]
2020-05-09 8:23 ` Andrew Pam
2020-05-09 20:28 ` Chris Murphy
2020-05-09 20:39 ` Andrew Pam
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=mu6h7cyw.fsf@gmx.com \
--to=damenly_su@gmx.com \
--cc=andrew@sericyb.com.au \
--cc=g.btrfs@cobb.uk.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.