From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Adam Borowski <kilobyte@angband.pl>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: warn about RAID5/6 being experimental at mount time
Date: Wed, 29 Mar 2017 21:27:32 +0200 [thread overview]
Message-ID: <1490815652.16829.3.camel@scientia.net> (raw)
In-Reply-To: <20170329043940.23655-1-kilobyte@angband.pl>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Wed, 2017-03-29 at 06:39 +0200, Adam Borowski wrote:
> Too many people come complaining about losing their data -- and
> indeed,
> there's no warning outside a wiki and the mailing list tribal
> knowledge.
> Message severity chosen for consistency with XFS -- "alert" makes
> dmesg
> produce nice red background which should get the point across.
Wouldn't it be much better to disallow:
- creation
AND
- mounting
of btrfs unless some special swtich like:
--yes-i-know-this-is-still-extremely-experimental
is given for the time being?
Normal users typically don't look at any such kernel log messages - and
expert users (who do) anyway know, that it's still unstable.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-03-29 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 4:39 [PATCH 1/2] btrfs: warn about RAID5/6 being experimental at mount time Adam Borowski
2017-03-29 4:39 ` [PATCH 2/2] btrfs: clear the RAID5/6 incompat flag once no longer needed Adam Borowski
2017-03-29 19:27 ` Christoph Anton Mitterer [this message]
2017-03-29 19:42 ` [PATCH 1/2] btrfs: warn about RAID5/6 being experimental at mount time Adam Borowski
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=1490815652.16829.3.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=dsterba@suse.com \
--cc=kilobyte@angband.pl \
--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