public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
To: Gregory Maxwell <gmaxwell@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 21:18:00 +0400	[thread overview]
Message-ID: <2a31deca0904201018t3635d08am9397a6d0a18aa1cc@mail.gmail.com> (raw)
In-Reply-To: <e692861c0904201008q7b5484cbt902587640c17c5d9@mail.gmail.com>

On Mon, Apr 20, 2009 at 9:08 PM, Gregory Maxwell <gmaxwell@gmail.com> w=
rote:
> On Mon, Apr 20, 2009 at 12:57 PM, Andrey Kuzmin
> <andrey.v.kuzmin@gmail.com> wrote:
>> On Mon, Apr 20, 2009 at 8:10 PM, Ahmed Kamal
>> <email.ahmedkamal@googlemail.com> wrote:
>>>> =C2=A0But now Oracle can re-license Solaris and merge ZFS with btr=
fs.
>>>> Just kidding, I don't think it would be technically feasible.
>>>>
>>>
>>> May I suggest the name "ZbtrFS" :)
>>> Sorry couldn't resist. On a more serious note though, is there any
>>> technical benefits that justify continuing to push money in btrfs
>>
>> 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 =C2=A0(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 =C2=A0and other featu=
res;
>> btrfs is free from both.
>
> I'm sure that people with far more experience than I will comment=E2=80=
=94
> But considering that BTRFS is in the Linux Kernel today, the historie=
s
> of other imported FSes (XFS),

Imported file-systems (someone more experienced may correct me if I'm
wrong) have previously been give-aways. This one is different - zfs is
in active development, with highly welcomed features like
de-duplication coming.

> and the state of ZFS in FreeBSD this may not be strictly true.

This was one-man's effort (though a heroic one, definitely), hardly a
case to compare with.


Regards,
Andrey
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-20 17:18 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 [this message]
2009-04-20 17:20           ` Chris Mason
2009-04-20 17:39       ` Alex Elsayed
2009-04-21  2:27       ` Eric Anopolsky
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=2a31deca0904201018t3635d08am9397a6d0a18aa1cc@mail.gmail.com \
    --to=andrey.v.kuzmin@gmail.com \
    --cc=email.ahmedkamal@googlemail.com \
    --cc=gmaxwell@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