You’ve got the hardware correct. Each datamover is also a blade, also called an xBlade.  Starting from the disk and going up…  Physical Disk RAID Group (collection of physical disks) LUN (block volume carved from a RAID Group, typically 2 or more from each RAID Group when using Celerra, evenly split among the two SPs) Celerra Volume (celerra representation of LUNs) Storage Pool (a collection of volumes) Filesystem (volume carved from a storage pool)  There are actually several types of volumes on a Celerra and some types are made from others…  Disk Volume = equivalent to a LUN presented from the backend storage to the datamover Slice = used to break a volume into smaller pieces which can be used for multiple filesystems Stripe = a collection of volumes on which data is striped evenly for good performance Meta = a collection of volumes combined together by concatenation  When using AVM (Automatic Volume Management) I believe the default storage pool on a Celerra is just a Meta of the available disk volumes. Filesystems are allocated from the individual LUNs(Disk Volumes) in the pool as they are created in a sort of round robin fashion. Performance is good but read/writes do not necessarily hit all disks in the pool.  If you use MVM (Manual Volume Management) you can build a storage pool using a combination of the above listed volumes. Depending on your requirements, you can get better performance using MVM. For example, if you had 2 LUNs per RAID Group, you could create two Stripe Volumes, each made from 1 Disk Volume per RAID Group. Then concatenate the two Stripes into a single Meta Volume. You can create filesystems from the Meta directly or you can create multiple Slice volumes from the Meta in order to provide more granular allocation of the space to the filesystems.  Typically, AVM provides adequate performance for 95% of workloads.  I hope that helps.
Celerra concepts and information