Ok, I deleted the volumes and now the "potential storage available" property increased. So far so good. I will just have to wait and see what happens when a file system expansion occurs. Hopefully, the storage pool pulls the new disks in. Unfortunately, I can't do a system rescan now because of a bad drive. I will get that fixed ASAP.

Thanks.

system pool will automatically select volumes based on specific criteria, since you decided to do your own slicing an dicing it does not like accept them into system pool anymore. If you want to use system pool/AVM ..delete all the components that you manually created and then rescan again and it should pick them up (granted LUNs that you created match system pool profiles).

In the GUI go to Storage and hit Rescan

Thank you!

I have been trying to find confirmation on the same question for a while. Glad to find this thread.

Just to review, the system defined file storage pools will automatically extending using the new LUNs as long as they meet the same storage profile. In my scenario, it's a RAID 5 (4+1) FC RAID group. I also have the option to create an entirely new file storage pool using the new LUNs, correct?

Thanks

Correct on both counts.  The system-defined file storage pools will extend using the new LUNs, if they're the same profile.  You can also decide to create an entirely new file storage pool with those devices as well.  Either way, it's up to you.  If you don't want to micromanage pool utilization, I recommend relying on the system-defined pools.  Continue to create new LUNs with matching profiles, and you can easily grow them as needed.

Ok, thanks.

By profile you mean LUN size and SP ownership? I usually add LUNs to the Celerra in pairs, same size and one on each SP.