linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Marat Khalili <mkh@rqc.ru>,
	waxhead@dirtcellar.net, linux-btrfs@vger.kernel.org
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Subject: Re: Tiered storage?
Date: Wed, 15 Nov 2017 07:43:29 -0500	[thread overview]
Message-ID: <dd42ed30-7bd1-cc1a-0f78-4920d3181411@gmail.com> (raw)
In-Reply-To: <8d8b22c1-3e20-64ab-f79f-f9dc3a4060ac@rqc.ru>

On 2017-11-15 04:26, Marat Khalili wrote:
> 
> On 15/11/17 10:11, waxhead wrote:
>> hint: you need more than two for raid1 if you want to stay safe
> Huh? Two is not enough? Having three or more makes a difference? (Or, 
> you mean hot spare?)
They're probably referring to an issue where a two device array 
configured for raid1 which had lost a device and was mounted degraded 
and writable would generate single profile chunks on the remaining 
device instead of a half-complete raid1 chunk.  This, when combined with 
the fact that older kernels only check the filesystem as a whole for 
normal/degraded/irreparable instead of checking individual chunks would 
refuse to mount the resultant filesystem, meant that you only had one 
chance to fix such an array.

If instead you have more than two devices, regular complete raid1 
profile chunks are generated, and it becomes a non-issue.

The second issue (checking degraded status at the chunk level instead of 
volume level) has been fixed in the most recent kernels.

The first issue has not been fixed yet, but I'm pretty sure there are 
patches pending.

  reply	other threads:[~2017-11-15 12:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15  1:01 Tiered storage? Roy Sigurd Karlsbakk
2017-11-15  7:11 ` waxhead
2017-11-15  9:26   ` Marat Khalili
2017-11-15 12:43     ` Austin S. Hemmelgarn [this message]
2017-11-15 12:52   ` Austin S. Hemmelgarn
2017-11-15 14:10     ` Roy Sigurd Karlsbakk
2017-11-15 22:09       ` Duncan
2017-11-16 16:42   ` Kai Krakow

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=dd42ed30-7bd1-cc1a-0f78-4920d3181411@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mkh@rqc.ru \
    --cc=roy@karlsbakk.net \
    --cc=waxhead@dirtcellar.net \
    /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).