Just look at the "Managing Celerra Volumes and File Systems Manually" manual.  From a support point of view, there is no restriction how many "equal" luns (same disks, same lun size and same raid type) to use for a filesystem. Even if not all combinations are a good idea.  Also think about a later filesystem extension.F.e. if the original FS is stripped across 30 Luns, any extension with less than 30 Luns will decrease the performance.  And if you stripe across many spindles for performance reason, but use only part of the stripe for the performance FS (slice it out of this stripe), think about not using the unused part, because if another FS will be located there it will increase the load of the spindles "needed" for the first FS.  If you decide to use a custom defined pool (from a Celerra wording) do not put Luns or the Celerra dvols (f.e. d37) into this pool. Instead create a volume of stripped dvols and put this into the pool. Because else AVM will concat dvols and you will not reach the expected performance.
Customer has a Celerra NS-120 supporting VMware data stores on NFS.  The underlying file system is created on an AVM-provisioned R1+0 volume spread across a number of 2-disk R1 volumes on the underlying CX4.    This datastore experiences severe latency issues, and I believe it is because the Celerra has put most of the operational data on just a few of the underlying disks.  i.e. the I/O workload is not being evenly distributed across the underlying d-vols.  I'd like to work with the customer to tear down the file system, and re-create the d-vols on native R1+0 provided by the CLARiiON, to get a true workload distribution. across the disks.  Looking at the documentation, is seems that native, more-than-two-disk, R1+0 is not supported by the Celerra.  However, I thought that this had been supported in later DART releases.  Can someone clarify?  Thanks, Eric
Celerra R1+0 - 2 disk support only???