From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unmountable Array After Drive Failure During Device Deletion
Date: Fri, 27 Dec 2013 10:18:38 +1100 [thread overview]
Message-ID: <7762191.E7zsbxQLzq@quad> (raw)
In-Reply-To: <pan$ba575$c4e4093$f5b3203$522a159c@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Sun, 22 Dec 2013 11:35:53 AM Duncan wrote:
> While the btrfs kernel config option no longer (as of 3.12 IIRC) directly
> calls the filesystem unstable
It'll be in 3.13, the commit was:
$ git describe 4204617d142c0887e45fda2562cb5c58097b918e
v3.12-116-g4204617
The help text for btrfs now says:
Btrfs is a general purpose copy-on-write filesystem with extents,
writable snapshotting, support for multiple devices and many more
features focused on fault tolerance, repair and easy administration.
The filesystem disk format is no longer unstable, and it's not
expected to change unless there are strong reasons to do so. If there
is a format change, file systems with a unchanged format will
continue to be mountable and usable by newer kernels.
For more information, please see the web pages at
http://btrfs.wiki.kernel.org.
cheers,
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 --]
prev parent reply other threads:[~2013-12-26 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 9:26 Unmountable Array After Drive Failure During Device Deletion Chris Kastorff
2013-12-19 18:07 ` Duncan
2013-12-19 19:16 ` Chris Kastorff
2013-12-19 19:41 ` Chris Kastorff
2013-12-19 22:21 ` Chris Murphy
2013-12-20 0:06 ` Chris Kastorff
2013-12-20 3:47 ` Chris Murphy
2013-12-21 23:16 ` Chris Kastorff
2013-12-21 23:40 ` Chris Murphy
2013-12-22 1:15 ` ronnie sahlberg
2013-12-22 11:35 ` Duncan
2013-12-26 23:18 ` Chris Samuel [this message]
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=7762191.E7zsbxQLzq@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;
as well as URLs for NNTP newsgroup(s).