From: Tomasz Chmielewski <tch@virtall.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Questions on using BtrFS for fileserver
Date: Wed, 20 Aug 2014 11:23:26 +0200 [thread overview]
Message-ID: <0f416a00a2dabac75caa768581a5e965@admin.virtall.com> (raw)
>> we are thinking about using BtrFS on standard hardware for a
>> fileserver with about 50T (100T raw) of storage (25×4TByte).
>>
>
> I would recommend carefully reading this thread titled: "1 week to
> rebuid 4x 3TB raid10 is a long time!"
So I have a 2 x 2.6 TB devices in btrfs RAID-1, 716G used. Linux 3.16.
One of the disks failed.
"btrfs device delete missing /home" is taking 9 days so far, on an idle
system:
root 4828 0.3 0.0 17844 260 pts/1 D+ Aug11 38:18 btrfs
device delete missing /home
There is some kind of btrfs debug info printed in dmesg which seems to
tell me that the operation is working, like:
[744657.598810] BTRFS info (device sda4): relocating block group
908951814144 flags 17
[744672.021612] BTRFS info (device sda4): found 4784 extents
[744688.604997] BTRFS info (device sda4): found 4784 extents
[744689.133397] BTRFS info (device sda4): relocating block group
910025555968 flags 17
[744701.162678] BTRFS info (device sda4): found 4196 extents
[744725.000459] BTRFS info (device sda4): found 4196 extents
but other than that, the recovery time doesn't look optimistic to me,
there is no ability to check the progress etc.
--
Tomasz Chmielewski
http://www.sslrack.com
next reply other threads:[~2014-08-20 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 9:23 Tomasz Chmielewski [this message]
2014-08-20 13:41 ` Questions on using BtrFS for fileserver Benjamin O'Connor
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 16:21 M G Berberich
2014-08-19 16:56 ` Kyle Manna
2014-08-19 19:05 ` Austin S Hemmelgarn
2014-08-19 21:09 ` Mitch Harder
2014-08-19 21:38 ` Andrej Manduch
2014-08-20 15:23 ` Austin S Hemmelgarn
2014-08-19 21:50 ` Roman Mamedov
2014-08-20 3:22 ` Marc MERLIN
2014-08-21 20:20 ` Andrew E. Mileski
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=0f416a00a2dabac75caa768581a5e965@admin.virtall.com \
--to=tch@virtall.com \
--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).