From: "Avi Miller" <avi.miller@gmail.com> Hi,

...

...

On 31 Oct 2014, at 9:58 am, Peter Ross <Petros.Listig@fdrive.com.au> wrote:

The article also mentions some speed issues especially in relation to databases.

...

The standard installation configured plain ext(ext3, I think but not sure) filesystems on a standalone server and later warned me about using it as the storage space for the VM disks (unfortunately I forgot exactly what it was, it was about "missing features" on it - and it was not the obvious about local storage which is not shared).

Local storage on Oracle VM is ext3 because it only stores the Dom0 software. The actual VM disk storage is either on OCFS2 (on FC/iSCSI shared storage) or NFS. We require OCFS2 for its clustering capabilities. You can use extra local storage as VM disk storage on Oracle VM 3.3 now too, which is also formatted OCFS2.

I expected this. I did not give the install a SAN disk and it took all available diskspace to format with ext3. Maybe I just forgot to click/unclick something during installation, not sure. I made a "dumb install" and thought: Let it take care of the details, don't change defaults.

Because it's a subvolume. :) It's not a filesystem, because subvolumes appear in their parent volumes, but can also be mounted independently.

<nit-picking> I never mount volumes, I mount filesystems. According to "Unix philosophy", it does not matter where filesystems are, you can mount them everywhere in a filesystem tree which has one root. And the btrfs default is mounting in the parent .. filesystem which is on the same pool. </nit-picking> Regards Peter