From: Andrew McGlashan <andrew.mcglashan@affinityvision.com.au>
To: Avi Miller <avi.miller@oracle.com>
Cc: Casper Bnag <casper.bang@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Experiences: Why BTRFS had to yield for ZFS
Date: Wed, 19 Sep 2012 02:48:08 +1000 [thread overview]
Message-ID: <5058A5C8.8080107@affinityvision.com.au> (raw)
In-Reply-To: <55422103-3EA7-4DE9-9C47-351CBD006871@oracle.com>
Hi,
On 17/09/2012 8:05 PM, Avi Miller wrote:
> Oracle Database is not certified to run on either btrfs or ZFS on Linux, so if certification is an issue, you can't use either filesystem. Out of interest, have you done a performance benchmark with ASM using ASMlib on the same platform?
I thought that Oracle considered BTRFS to be production ready. It
surprises me that running an Oracle database on BTRFS is not a supported
configuration.
Cheers
--
Kind Regards
AndrewM
Andrew McGlashan
Broadband Solutions now including VoIP
Current Land Line No: 03 9012 2102
Mobile: 04 2574 1827 Fax: 03 9012 2178
National No: 1300 85 3804
Affinity Vision Australia Pty Ltd
http://affinityvision.com.au
http://securemywireless.com.au
http://adsl2choice.net.au
In Case of Emergency -- http://affinityvision.com.au/ice.html
next prev parent reply other threads:[~2012-09-18 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 8:45 Experiences: Why BTRFS had to yield for ZFS Casper Bang
2012-09-17 9:15 ` Ralf Hildebrandt
2012-09-17 9:55 ` Casper Bnag
2012-09-17 10:05 ` Avi Miller
2012-09-17 10:47 ` Casper Bnag
2012-09-17 10:58 ` Avi Miller
2012-09-18 16:48 ` Andrew McGlashan [this message]
2012-09-18 21:46 ` Avi Miller
2012-09-18 5:28 ` Anand Jain
2012-09-19 7:28 ` Casper Bang
2012-09-19 7:36 ` Fajar A. Nugraha
2012-09-19 8:09 ` Casper Bang
2012-09-18 23:08 ` Gregory Farnum
2012-09-19 15:25 ` Chris Mason
2012-09-19 19:43 ` Casper Bang
2012-10-08 14:38 ` Casper Bang
2012-10-08 20:59 ` Avi Miller
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=5058A5C8.8080107@affinityvision.com.au \
--to=andrew.mcglashan@affinityvision.com.au \
--cc=avi.miller@oracle.com \
--cc=casper.bang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.