> > If the servers don't need to access the storage as a block > device, why not just NAS / NFS? That reduces the complexity > even further. :) >
For a couple of reasons, mostly to do with failure prevention. As Ernest replied, with NFS you end up with a single point of failure. Unless you build in some NFS redundancy with failover. But again you are increasing complexity and cost (additional servers required as the redundant NFS heads). As some list members have mentioned this can be achieved (with a NetAPP NFS cluster or similar), but unfortunately that is not something we can really justify. So it seemed to make sense to allow the development servers to access a single central data repository, and hence my queries regarding the performance of OCFS2 with *regular* data over regular services (as if there is such a thing). Thanks for the replies and opinions, I guess I'll just have to do some testing of OCFS2 and GFS on my test rig :) Dan-- Dan Hawker Linux System Administrator Astrium -- This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. --------------------------------------------------------------------- Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England _______________________________________________ Ocfs2-users mailing list [email protected] http://oss.oracle.com/mailman/listinfo/ocfs2-users
