From: Bardur Arantsson <spam@scientician.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs across a mix of SSDs & HDDs
Date: Wed, 02 May 2012 04:22:17 +0200 [thread overview]
Message-ID: <jnq5os$tdn$1@dough.gmane.org> (raw)
In-Reply-To: <jnpdud$ta9$1@dough.gmane.org>
On 05/01/2012 09:35 PM, Martin wrote:
> How well does btrfs perform across a mix of:
>
> 1 SSD and 1 HDD for 'raid' 1 mirror for both data and metadata?
>
> Similarly so across 2 SSDs and 2 HDDs (4 devices)?
>
> Can multiple (small) SSDs be 'clustered' as one device and then mirrored
> with one large HDD with btrfs directly? (Other than using lvm...)
>
>
> The idea is to gain the random access speed of the SSDs but have the
> HDDs as backup in case the SSDs fail due to wear...
>
> The usage is to support a few hundred Maildirs + imap for users that
> often have many thousands of emails in the one folder for their inbox...
>
>
> (And no, the users cannot be trained to clean out their inboxes or to be
> more hierarchically tidy... :-( )
>
> Or is btrfs yet too premature to suffer such use?
>
From Kconfig:
"Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^
Btrfs is too immature to use in ANY kind of production-like scenario
where you cannot afford to lose a certain amount of data (i.e. be forced
to restore from backup) AND suffer downtime.
I don't think email users are going to be thrilled about the prospect of
"lossy" email.
(Not that the other questions aren't valid.)
Regards,
next prev parent reply other threads:[~2012-05-02 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:35 btrfs across a mix of SSDs & HDDs Martin
2012-05-01 21:16 ` sam tygier
2012-05-02 0:56 ` Martin
2012-05-02 2:22 ` Bardur Arantsson [this message]
2012-05-02 4:28 ` Fajar A. Nugraha
2012-05-02 5:00 ` Bardur Arantsson
2012-05-02 5:30 ` Fajar A. Nugraha
2012-05-02 14:00 ` Martin
2012-05-02 18:41 ` Duncan
2012-05-02 23:54 ` vivo75
2012-05-03 0:46 ` Duncan
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='jnq5os$tdn$1@dough.gmane.org' \
--to=spam@scientician.net \
--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.