linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: David Nicol <davidnicol@gmail.com>
Subject: Re: remote mirroring in the works?
Date: Mon, 06 Sep 2010 17:04:02 -0700	[thread overview]
Message-ID: <4C858172.3020602@noir.com> (raw)
In-Reply-To: <AANLkTikze-2DsoMb6h-hvz4H8CPpHgxUqx7vCaOyV7+p@mail.gmail.com>

  On 20100906 14:50, David Nicol wrote:
> Only off-topic if BTRFS isn't ever going to ooze into the space
> currently occupied by the likes of
>
> http://en.wikipedia.org/wiki/Global_File_System
>
> that is, file systems that have multiple nodes simultaneously
> accessing block devices and tolerating faults.

There seem to be a number of other systems looking at building fault 
tolerance and distribution over btrfs: crfs, ceph, lustre.  I'm 
convinced that will happen even if btrfs doesn't do it natively.

Btrfs could probably be built to stripe and/or mirror over several nbd 
devices now, although I haven't tried it.

--rich

  reply	other threads:[~2010-09-07  0:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinmSdHwXXq3s64sM39GjacafgwgTjPadZGHuway@mail.gmail.com>
2010-08-30 17:07 ` remote mirroring in the works? Fred van Zwieten
2010-08-30 17:21   ` Bryan Whitehead
2010-08-30 17:33   ` Roy Sigurd Karlsbakk
2010-08-30 17:55   ` K. Richard Pixley
2010-08-30 17:59     ` Roy Sigurd Karlsbakk
2010-08-30 18:14       ` K. Richard Pixley
2010-08-31  6:30         ` Simon Kirby
2010-08-31 18:44           ` Fred van Zwieten
2010-09-06 21:50         ` David Nicol
2010-09-07  0:04           ` K. Richard Pixley [this message]
2010-08-30 21:15     ` Fred van Zwieten
2010-08-30 21:23       ` Freddie Cash
2010-08-30 22:56       ` K. Richard Pixley
2010-08-31  5:07         ` Fred van Zwieten
2010-08-31  6:38           ` Simon Kirby
2010-08-31 18:29             ` Goffredo Baroncelli

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=4C858172.3020602@noir.com \
    --to=rich@noir.com \
    --cc=davidnicol@gmail.com \
    /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).