From: Eric Anopolsky <erpo41@gmail.com>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: Ahmed Kamal <email.ahmedkamal@googlemail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs development plans
Date: Mon, 20 Apr 2009 20:27:39 -0600 [thread overview]
Message-ID: <1240280859.16733.13.camel@telesto> (raw)
In-Reply-To: <2a31deca0904200957v39badd2eu4b26844e78fdcde3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Mon, 2009-04-20 at 20:57 +0400, Andrey Kuzmin wrote:
>
> Personally, I don't see any. Porting zfs to Linux will cost (quite)
> some time and effort, but this is peanuts compared to what's needed to
> get btrfs (no offense meant) to maturity level/feature parity with
> zfs. The only thing that could prevent this is CDDL licensing issues
> and patent claims from NTAP over zfs snapshots and other features;
> btrfs is free from both.
>
In case anyone is interested, ZFS already has been ported to Linux as a
FUSE module. A very talented GSoC participant did the port as his
project. It works pretty well, but AFAIK it's not quite suitable for a
root filesystem yet. Still, much of the hard work has been done.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2009-04-21 2:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 14:37 Btrfs development plans Chris Mason
2009-04-20 15:31 ` Tomasz Torcz
2009-04-20 16:10 ` Ahmed Kamal
2009-04-20 16:38 ` Chris Mason
2009-04-21 7:46 ` Stephan von Krawczynski
2009-04-21 8:56 ` Dmitri Nikulin
2009-04-21 15:05 ` ashford
2009-04-20 16:57 ` Andrey Kuzmin
2009-04-20 17:08 ` Gregory Maxwell
2009-04-20 17:18 ` Andrey Kuzmin
2009-04-20 17:20 ` Chris Mason
2009-04-20 17:39 ` Alex Elsayed
2009-04-21 2:27 ` Eric Anopolsky [this message]
2009-05-24 12:13 ` Chris Samuel
2009-04-20 18:42 ` Ric Wheeler
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=1240280859.16733.13.camel@telesto \
--to=erpo41@gmail.com \
--cc=andrey.v.kuzmin@gmail.com \
--cc=email.ahmedkamal@googlemail.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