public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Sat, 04 Jan 2014 22:28:03 +1100	[thread overview]
Message-ID: <1422900.iO9oO96QZb@quad> (raw)
In-Reply-To: <CAAVQaYBZS87S7XNdDpUv5pBMvqF0+th34H8PjSLVLtZV9LOR=Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

On Sat, 4 Jan 2014 12:57:02 AM Dave wrote:

> I find myself annoyed by the constant disclaimers I
> read on this list, about the experimental status of Btrfs, but it's
> apparent that this hasn't sunk in for everyone.

Btrfs will no longer marked as experimental in the kernel as of 3.13.

Unless someone submits a patch to fix it first. :-)

Can we also keep things polite here please.

thanks,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2014-01-04 11:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 22:28 btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT Jim Salter
2014-01-03 22:42 ` Emil Karlson
2014-01-03 22:43 ` Joshua Schüler
2014-01-03 22:56   ` Jim Salter
2014-01-03 23:04     ` Hugo Mills
2014-01-03 23:04     ` Joshua Schüler
2014-01-03 23:13       ` Jim Salter
2014-01-03 23:18         ` Hugo Mills
2014-01-03 23:25           ` Jim Salter
2014-01-03 23:32             ` Chris Murphy
2014-01-03 23:22         ` Chris Murphy
2014-01-04  6:10           ` Duncan
2014-01-04 11:20             ` Chris Samuel
2014-01-04 13:03               ` Duncan
2014-01-04 14:51             ` Chris Mason
2014-01-04 15:23               ` Goffredo Baroncelli
2014-01-04 20:08               ` Duncan
2014-01-04 21:22             ` Jim Salter
2014-01-05 11:01               ` Duncan
2014-01-03 23:19     ` Chris Murphy
     [not found]     ` <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
2014-01-03 23:42       ` Jim Salter
2014-01-03 23:45         ` Jim Salter
2014-01-04  0:27         ` Chris Murphy
2014-01-04  2:59           ` Jim Salter
2014-01-04  5:57             ` Dave
2014-01-04 11:28               ` Chris Samuel [this message]
2014-01-04 14:56                 ` Chris Mason
2014-01-05  9:20                   ` Chris Samuel
2014-01-05 11:16                     ` Duncan
2014-01-04 19:18             ` Chris Murphy
2014-01-04 21:16               ` Jim Salter
2014-01-05 20:25                 ` Chris Murphy
2014-01-06 10:20                   ` Chris Samuel
2014-01-06 18:30                     ` Chris Murphy
2014-01-06 19:25                       ` Jim Salter
2014-01-06 22:05                         ` Chris Murphy
2014-01-06 22:24                           ` Jim Salter
2014-01-07  5:43                         ` Chris Samuel
2014-01-06 19:31                       ` correct way to rollback a root filesystem? Jim Salter
2014-01-07 11:55                         ` Sander

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=1422900.iO9oO96QZb@quad \
    --to=chris@csamuel.org \
    --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