Allocation owner of a pool LUN is the SP that owns and maintains the metadata for that LUN. It is not advised to trespass the LUNs to an SP that is not the allocation owner. This introduces lag.  As defined in the Unisphere help---  The SP that provides the best performance for the pool LUN. The allocation owner SP is set by the system to match the default SP owner when you create the LUN. You cannot change the allocation owner after the LUN is created. If you change the default owner for the LUN, the software will display a warning that a performance penalty will occur if you continue.  Default owner can be cahnged post LUN creation. So what probably happened was that you created a LUN with default SP as SP-A, which was set to be the allocation owner too. Somehow, someone changed the default owner to SP-B. In your case, you should revert default ownership of the said LUN to SP-A.  HTH. Cheers, -joji
I created a virtual pool of 50 disks - raid5. in creating a lun, it was defaulting to Default Owner - Auto. I deselected that option and manually chose an owner SP for my multiple luns I created as I wanted to balance SP ownership. When I look at the luns individually, they have the Currrent Owner and Allocation Owner as SPA but the Default Owner as SPB. I trespassed that particular lun to SPB but am I doing the correct thing here?  What is Allocation Owner and in a virtual pool, do all luns have to be either on Auto for SP Owner or owned by the same SP?  thanks.
flare30 virtual provisioning question