From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Chris Murphy'" <lists@colorremedies.com>
Cc: "'Btrfs BTRFS'" <linux-btrfs@vger.kernel.org>
Subject: RE: Odd output from scrub status
Date: Tue, 19 Jul 2022 01:01:29 +0100 [thread overview]
Message-ID: <009001d89b02$b7f2eb60$27d8c220$@perdrix.co.uk> (raw)
In-Reply-To: <CAJCQCtTAx=82boq175vtAu1Z_S9D1tcNSErir1wTK8MbtMfsvw@mail.gmail.com>
btrfs-progs 5.4.1-2
-----Original Message-----
From: Chris Murphy <lists@colorremedies.com>
Sent: 18 July 2022 20:51
To: David C. Partridge <david.partridge@perdrix.co.uk>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Odd output from scrub status
On Sun, Jul 17, 2022 at 7:28 AM David C. Partridge
<david.partridge@perdrix.co.uk> wrote:
>
> root@charon:~/bin# btrfs scrub status /dev/sdb1
> UUID: f9655777-8c81-4d5e-8f14-c1906b7b27a3
> Scrub started: Sun Jul 17 10:27:39 2022
> Status: running
> Duration: 1:59:29
> Time left: 6095267:46:37
> ETA: Tue Nov 20 23:13:45 2717
> Total to scrub: 4.99TiB
> Bytes scrubbed: 5.48TiB
> Rate: 801.72MiB/s
> Error summary: no errors found
> root@charon:~/bin#
What version of btrfs-progs? Looks like 96ed8e801 fixed an issue with
ETA reporting, which I'm guessing made it into btrfs-progs 5.2 or
5.2.1?
--
Chris Murphy
next prev parent reply other threads:[~2022-07-19 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:28 Odd output from scrub status David C. Partridge
2022-07-18 8:01 ` Nikolay Borisov
2022-07-18 9:13 ` David C. Partridge
2022-07-18 8:05 ` Qu Wenruo
2022-07-18 9:18 ` David C. Partridge
2022-07-18 19:50 ` Chris Murphy
2022-07-19 0:01 ` David C. Partridge [this message]
2022-07-19 3:35 ` Chris Murphy
2022-07-19 16:32 ` David C. Partridge
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='009001d89b02$b7f2eb60$27d8c220$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox