The issue seems to be with removing the shelf from the current filer. We support hot 'adds,, but not hot 'removes.'.
But there are other things to consider as well, such as the volume or aggregate association of the disks in the shelf you will remove and the resulting state of vol0 or the containing aggregate thereof.
So if any disk belonging to vol0 or that aggregate are in that shelf, you need to do some swapping around during that outage where you will have to shutdown the existing head to remove the shelf and 'hot add' it to the other head.
I would call the support center regardless to ensure no steps or caveats are missed as their resources and skills scale best for these procedures.
Good luck ....
Pardon brevity, typos, etc; sent from mobile.
-----Original Message----- From: Peta Spies [mailto:peta.spies@gmail.com] Sent: Monday, April 21, 2008 03:44 AM Pacific Standard Time To: toasters@mathworks.com Subject: Balanced clusters?
Hi,
We normally build our clusters as per (what I believe is) best practice, with equal number of identical shelves on each loop. However, we've hit an emergency situation where a currently unused (and not in the aggr) shelf on one head would really really really be much more useful on the other, to grow a very full volume on there.
Due to the nature of the problem, just presenting a new volume from this shelf is not a good enough fix; I need to grow the existing volume. Asap.
So how bad of an idea would it be to wire that shelf into the other head? Will the cluster complain? The cluster in question is a 3040C, and we'll end up with 3 sata shelves on one head and 1 on the other.
Peta