On 3/28/2013 8:21 AM, Jan Perci wrote: > Normally I would use raw mappings and XFS directly on the volumes. But > there is a hard requirement to support VM snapshots, so all the data must > reside within VMDK files on the VMFS datastores. Since when? ESX has had LUN snapshot capability back to 3.0, 6 years or so. It may have required the VCB add on back then. Is this simply a limitation of the freebie version? If so, pony up and pay for what you need, or switch to a FOSS solution which has no such limitations. VMFS volumes are not intended for high performance IO. Unless things have changed recently, VMware has always recommended housing only OS images and the like in VMDKs, not user data. They've always recommended using RDMs for everything else. IIRC VMDKs have a huge block (sector) size, something like 1MB. That's going to make XFS alignment difficult, if not impossible. I cannot stress emphatically enough that you should not stitch 2TB VMDKs together and use them in the manner you described. This is a recipe for disaster. Find another solution. -- Stan _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
