From: Stan Hoeppner <stan@hardwarefreak.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: question on new feature complexity/possibility/sensibility? (^ Alternate)
Date: Mon, 27 Jun 2011 03:22:50 -0500 [thread overview]
Message-ID: <4E083DDA.1000101@hardwarefreak.com> (raw)
In-Reply-To: <20110627060240.GF32466@dastard>
On 6/27/2011 1:02 AM, Dave Chinner wrote:
> On Sun, Jun 26, 2011 at 09:08:41PM -0700, Linda Walsh wrote:
>>
>>
>> Dave Chinner wrote:
>>> So use a filesystem that supports them natively ;)
>> ---
>> Got any in in mind that also support acls, extended attrs
>> and has the reliability and performance of xfs? ;-)
>
> For most "normal" workloads, ZFS would probably be your only
> production ready option. But that's not something you could use on
> Linux, is it? :/
It is apparently usable on Linux for those willing to build and maintain
it themselves. But that level of administrative burden in itself is the
opposite of production ready.
> Until btrfs is a completely baked cake, you won't be able to tick
> all those boxes, and even then there will be questions about
> performance...
Or until Oracle releases ZFS under GPL, or a compatible license, which
probably isn't going to happen. Apparently Oracle believes their SPARC
and x86 hardware won't sell if ZFS is free on Linux. Now that Oracle
owns Solaris and ZFS I'd bet they wish they could put the BTRFS genie
back in the bottle, as well as OCFS, etc.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-06-27 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 0:29 question on new feature complexity/possibility/sensibility? (^ Alternate) Linda A. Walsh
2011-06-27 0:32 ` Dave Chinner
2011-06-27 4:08 ` Linda Walsh
2011-06-27 6:02 ` Dave Chinner
2011-06-27 8:22 ` Stan Hoeppner [this message]
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=4E083DDA.1000101@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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