From: "Ondřej Kunc" <ondrej.kunc@ignum.cz>
To: linux-btrfs@vger.kernel.org
Subject: Is parralel device remove possible ?
Date: Thu, 19 Sep 2013 09:58:35 +0200 [thread overview]
Message-ID: <523AAEAB.1020300@ignum.cz> (raw)
Hi,
I'm just removing about 8 drives from btrfs pool and I issued this command:
btrfs dev del /dev/sd[bmghkqps]
According to munin graphs it is removing drives sequentially and ... I
can see it is reading that drive which it is actually removing ... but
it is doing big writes(so it is probably moving data there) to other
drives which will be removed later.
Would it be possible to do this in parallel ... to restrict next writing
to drives to fasten this operation ?
Now it is running about 3 days and it has removed 5 drives.
And second question ... is there way how to see progress of drive
removing ? In dmesg I can see relocating block group ... and the number
of group is decreasing ... but sometimes it changes direction, so it
doesn't provide so useful estimation.
Thanks,
Ondřej
--
S pozdravem,
Ondřej Kunc, Senior Linux Administrator
IGNUM s.r.o., Vinohradská 190, Praha 3, 130 61, CZE
Mobil: +420 603 111 111 | Fax: +420 296 332 222
www.ignum.cz | www.domena.cz | www.webcloud.cz
reply other threads:[~2013-09-19 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=523AAEAB.1020300@ignum.cz \
--to=ondrej.kunc@ignum.cz \
--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).