From: Martin Steigerwald <Martin@lichtvoll.de>
To: george@chinilu.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Scrub CPU usage ...
Date: Sun, 05 May 2013 11:22:36 +0200 [thread overview]
Message-ID: <2221106.SQ983GtkxQ@merkaba> (raw)
In-Reply-To: <518555FF.4020704@chinilu.com>
Hi George!
Am Samstag, 4. Mai 2013, 11:39:59 schrieb George Mitchell:
> the next update. I am using btrfs raid 1 across five 500GB Seagate
> nearline drives and btrfs single on a Seagate 4TB backup drive. I am
> absolutely delighted with how this system is working. This is my
> primary day in and day out system. I have to date hard crashed this
> system at least three times without sustaining any apparent damage to
> the filesystems. Perhaps I have just been extremely lucky, but it seems
> like most of the major holes have been closed at this point. Actually I
> have only two significant issues currently with btrfs.
Are you aware that BTRFS RAID-1 works differently than block based RAID? BTRFS
will only be holding two copies of every data or metadata chunk on two
different drives, regardless how many drives you use. So only one drive may
fail.
Well, I think you will have notices with df output for the filesystem, but I
thought I mention it, just in case.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-05-05 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 18:39 Scrub CPU usage George Mitchell
2013-05-05 1:21 ` Kai Krakow
2013-05-05 1:58 ` George Mitchell
2013-05-05 9:22 ` Martin Steigerwald [this message]
2013-05-05 14:15 ` George Mitchell
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=2221106.SQ983GtkxQ@merkaba \
--to=martin@lichtvoll.de \
--cc=george@chinilu.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 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.