From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: linux-btrfs@vger.kernel.org
Subject: Re: Extremely slow device removals
Date: Thu, 30 Apr 2020 08:13:31 -1000 [thread overview]
Message-ID: <r8f4gb$8qt$1@ciao.gmane.io> (raw)
In-Reply-To: <14a8e382-0541-0f18-b969-ccf4b3254461@ka9q.net>
Le 30/04/2020 à 07:31, Phil Karn a écrit :
> I started the operation 5 days ago, and of right now I still have 2.18
> TB to move off the drive I'm trying to replace. I think it started
> around 3.5 TB.
Hi Phil,
I did something similar one month ago. It took less than 4 hours for
1.71 TiB of data:
[xxx@taina ~]$ sudo btrfs replace status /home/SysNux
Started on 21.Mar 11:13:20, finished on 21.Mar 15:06:33, 0 write errs, 0
uncorr. read errs
[xxxg@taina ~]$ sudo btrfs fi show /home/SysNux/
Label: none uuid: c5b8386b-b81d-4473-9340-7b8a74fc3a3c
Total devices 2 FS bytes used 1.70TiB
devid 1 size 1.82TiB used 1.71TiB path /dev/bcache2
devid 2 size 1.82TiB used 1.71TiB path /dev/bcache0
These disks are behind bcache, which may have a positive impact. Also my
system is Fedora 31, and it was with 5.5 kernel, much more recent than
yours.
> Should I reboot degraded without this drive and do a "remove missing"
> operation instead? I'm willing to take the risk of losing another drive
> during the operation if it'll speed this up. It wouldn't be so bad if it
> weren't slowing my filesystem to a crawl for normal stuff, like reading
> mail.
No idea, I'm just a (happy) Btrfs user.
Hope this helps,
--
Jean-Denis Girard
SysNux Systèmes Linux en Polynésie française
https://www.sysnux.pf/ Tél: +689 40.50.10.40 / GSM: +689 87.797.527
next prev parent reply other threads:[~2020-04-30 18:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 7:22 Extremely slow device removals Phil Karn
2020-04-30 17:31 ` Phil Karn
2020-04-30 18:13 ` Jean-Denis Girard [this message]
2020-05-01 8:05 ` Phil Karn
2020-05-02 3:35 ` Zygo Blaxell
[not found] ` <CAMwB8mjUw+KV8mxg8ynPsv0sj5vSpwG7_khw=oP5n+SnPYzumQ@mail.gmail.com>
2020-05-02 4:31 ` Zygo Blaxell
2020-05-02 4:48 ` Paul Jones
2020-05-02 5:25 ` Phil Karn
2020-05-02 6:04 ` Remi Gauvin
2020-05-02 7:20 ` Zygo Blaxell
2020-05-02 7:27 ` Phil Karn
2020-05-02 7:52 ` Zygo Blaxell
2020-05-02 6:00 ` Zygo Blaxell
2020-05-02 6:23 ` Paul Jones
2020-05-02 7:20 ` Phil Karn
2020-05-02 7:42 ` Zygo Blaxell
2020-05-02 8:22 ` Phil Karn
2020-05-02 8:24 ` Phil Karn
2020-05-02 9:09 ` Zygo Blaxell
2020-05-02 17:48 ` Chris Murphy
2020-05-03 5:26 ` Zygo Blaxell
2020-05-03 5:39 ` Chris Murphy
2020-05-03 6:05 ` Chris Murphy
2020-05-04 2:09 ` Phil Karn
2020-05-02 7:43 ` Jukka Larja
2020-05-02 4:49 ` Phil Karn
2020-04-30 18:40 ` Chris Murphy
2020-04-30 19:59 ` Phil Karn
2020-04-30 20:27 ` Alexandru Dordea
2020-04-30 20:58 ` Phil Karn
2020-05-01 2:47 ` Zygo Blaxell
2020-05-01 4:48 ` Phil Karn
2020-05-01 6:05 ` Alexandru Dordea
2020-05-01 7:29 ` Phil Karn
2020-05-02 4:18 ` Zygo Blaxell
2020-05-02 4:48 ` Phil Karn
2020-05-02 5:00 ` Phil Karn
2020-05-03 2:28 ` Phil Karn
2020-05-04 7:39 ` Phil Karn
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='r8f4gb$8qt$1@ciao.gmane.io' \
--to=jd.girard@sysnux.pf \
--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).