From: Martin Steigerwald <martin@lichtvoll.de>
To: Wilson Meier <wilson.meier@gmail.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Duncan <1i5t5.duncan@cox.net>,
linux-btrfs@vger.kernel.org
Subject: Re: Convert from RAID 5 to 10
Date: Wed, 30 Nov 2016 17:35:00 +0100 [thread overview]
Message-ID: <3704790.nMdNB9Lobq@merkaba> (raw)
In-Reply-To: <e9a4cba5-53b7-b6f0-af83-467f5f95f5b8@googlemail.com>
Am Mittwoch, 30. November 2016, 16:49:59 CET schrieb Wilson Meier:
> Am 30/11/16 um 15:37 schrieb Austin S. Hemmelgarn:
> > On 2016-11-30 08:12, Wilson Meier wrote:
> >> Am 30/11/16 um 11:41 schrieb Duncan:
> >>> Wilson Meier posted on Wed, 30 Nov 2016 09:35:36 +0100 as excerpted:
> >>>> Am 30/11/16 um 09:06 schrieb Martin Steigerwald:
> >>>>> Am Mittwoch, 30. November 2016, 10:38:08 CET schrieb Roman Mamedov:
[…]
> >> It is really disappointing to not have this information in the wiki
> >> itself. This would have saved me, and i'm quite sure others too, a lot
> >> of time.
> >> Sorry for being a bit frustrated.
>
> I'm not angry or something like that :) .
> I just would like to have the possibility to read such information about
> the storage i put my personal data (> 3 TB) on its official wiki.
Anyone can get an account on the wiki and add notes there, so feel free.
You can even use footnotes or something like that. Maybe it would be good to
add a paragraph there that features are related to one another, so while BTRFS
RAID 1 for example might be quite okay, it depends on features that are still
flaky.
I for myself rely quite much on BTRFS RAID 1 with lzo compression and it seems
to work okay for me.
--
Martin
next prev parent reply other threads:[~2016-11-30 16:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 17:20 Convert from RAID 5 to 10 Florian Lindner
2016-11-29 17:54 ` Austin S. Hemmelgarn
2016-11-29 22:34 ` Wilson Meier
2016-11-29 22:52 ` Chris Murphy
2016-11-29 23:16 ` Wilson Meier
2016-11-29 23:49 ` Chris Murphy
2016-11-29 23:58 ` Wilson Meier
2016-11-30 5:38 ` Roman Mamedov
2016-11-30 8:06 ` Martin Steigerwald
2016-11-30 8:35 ` Wilson Meier
2016-11-30 10:41 ` Duncan
2016-11-30 13:12 ` Wilson Meier
2016-11-30 14:37 ` Austin S. Hemmelgarn
2016-11-30 15:49 ` Wilson Meier
2016-11-30 16:35 ` Martin Steigerwald [this message]
2016-11-30 16:48 ` Austin S. Hemmelgarn
2016-12-01 6:47 ` Duncan
2016-12-01 9:37 ` Wilson Meier
2016-12-01 11:36 ` Niccolò Belli
2016-11-30 19:09 ` Chris Murphy
2016-11-30 19:36 ` Martin Steigerwald
2016-11-30 20:29 ` Tomasz Kusmierz
2016-12-01 17:28 ` Chris Murphy
2016-12-01 21:40 ` Tomasz Kusmierz
2016-11-30 16:09 ` Niccolò Belli
2016-11-30 12:50 ` Austin S. Hemmelgarn
2016-11-30 14:04 ` Roman Mamedov
2016-11-30 15:43 ` Austin S. Hemmelgarn
2016-11-30 18:59 ` Chris Murphy
2016-11-29 19:03 ` Lionel Bouton
2016-11-29 19:41 ` Austin S. Hemmelgarn
2016-12-06 14:14 ` Florian Lindner
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=3704790.nMdNB9Lobq@merkaba \
--to=martin@lichtvoll.de \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wilson.meier@gmail.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 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.