All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gert Menke <gert@menke.ac>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Switch raid mode without rebalance?
Date: Fri, 26 Aug 2016 21:53:55 +0200	[thread overview]
Message-ID: <adffdbf3b833f464a36a0e38a27d4608@durkon.lan> (raw)
In-Reply-To: <456dc4ab-f6ae-48d6-94d6-782e56e284e0@gmail.com>

Hi,

On 2016-08-26 13:52, Austin S. Hemmelgarn wrote:

> Regular 'df' isn't to be trusted when dealing with BTRFS, the only
> reason we report anything there is because many things break horribly
> if we don't.
Yeah, I noticed. Seems to produce a reasonable guess, though.

> Additionally, while running with multiple profiles while not balancing
> should work, it's pretty much untested, and any number of things may
> break.
Oh. Good to know.

> Assuming your two disks have similar latency and transfer
> speed, you're almost certainly better off just converting completely
> to single mode (which works like raid0, just at the chunk level
> instead of the block level).
Okay, I see.

> On a slightly separate note, if your doing backups more frequently
> than once a week, your probably better off just leaving the disks
> connected and running.  Regular load/unload cycles are generally
> harder on the mechanical components in modern disks than just leaving
> them running 24/7.
True. A bit of context: I first want to make a full backup locally, then 
use the disks off-site for nightly incremental backups via internet.

Cheers
Gert

  reply	other threads:[~2016-08-26 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 18:16 Switch raid mode without rebalance? Gert Menke
2016-08-25 18:26 ` Justin Kilpatrick
2016-08-25 22:32   ` Gert Menke
2016-08-26 11:52     ` Austin S. Hemmelgarn
2016-08-26 19:53       ` Gert Menke [this message]
2016-08-25 19:50 ` Chris Murphy
2016-08-25 22:33   ` Gert Menke
2016-08-25 23:04     ` Chris Murphy
2016-08-26 19:18       ` Gert Menke
2016-08-26 20:31         ` Chris Murphy

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=adffdbf3b833f464a36a0e38a27d4608@durkon.lan \
    --to=gert@menke.ac \
    --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.