Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Jim MacBaine <jmacbaine@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: raid1 on uneven-sized disks
Date: Sun, 9 Aug 2015 12:47:25 +0000	[thread overview]
Message-ID: <20150809124725.GA5486@carfax.org.uk> (raw)
In-Reply-To: <CAMoY8LpmhQtSvW-sWbGKDFKNN3xaKPwe+QxU5wCMg2Wcz3ObWA@mail.gmail.com>

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

On Sun, Aug 09, 2015 at 02:29:53PM +0200, Jim MacBaine wrote:
> Hi,
> 
> How does btrfs handle raid1 on a bunch of uneven sized disks? Can I
> just keep adding arbitrarily sized disks to an existing raid1 and
> expect the file system to continue to keep two copies of everything,
> so I could survive the loss of any single disk without data loss? Does
> btrfs work this way?

   Yes, exactly.

   You may find that http://carfax.org.uk/btrfs-usage/ is helpful.

   Hugo.

> For backing up several machines at home, I use an old Debian machine
> which is equipped with some spare disks I could get my hands on.
> Currently that would be 2 x 2TB, 1 x 1.5TB , 3 x 1TB disks.
> 
> Traditionally I'm using rsync to create hardlinked backups on ext3/4
> on md-raid1. This setup has been working reliably for many years now,
> including the survival of two disk failures. But it is quite
> cumbersome to reshape the structure of the raids when I get a new
> disk, an old one fails, or space requirements change. A single btrfs
> with snapshots would be much easier to handle. I'm not aiming for
> absolute reliability here -- all the really important stuff is backed
> up in a third place as well. But I would rather not like my file
> system to be the weakest link in the backup chain.
> 
> Regards,
> Jim

-- 
Hugo Mills             | Guards! Help! We're being rescued!
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |                       The Stainless Steel Rat Forever

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-08-09 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 12:29 raid1 on uneven-sized disks Jim MacBaine
2015-08-09 12:47 ` Hugo Mills [this message]
2015-08-10  2:25   ` Rich Freeman
2015-08-10  3:44     ` Duncan
2015-08-10  4:13 ` Duncan
2015-08-12 19:47   ` Jim MacBaine

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=20150809124725.GA5486@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=jmacbaine@gmail.com \
    --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