Help with Volume Expansion gone bad....

[macrobatix]

I'm working on adding two Promise expansion chassis to an XSan volume that already has 1 expansion chassis.



Adding the 2nd expansion chassis was easy, formatted fine, added two Affinities - Data and Data2

Added two luns D6, and D7 to Data, and added lun AS3 to Data2

Expanded the volume and all was fine. Volume size increased by about 11TB.

It didn't go so well with adding the third expansion chassis.

After the luns were created, I had 3 to add to the storage pools. D8, D9 and AS4.

Added D8 and D9 to "Data" so it had D6, D7, D8 and D9. All 4.55TB Luns

Added AS4 to Data2 so it had AS3 and AS4. Both 1.82TB Luns.

The process started, but never finished. It hung on unmounting volume forever, until the only way I could use the admin program again was to force quit.

Now- there are two Storage Pools that I never created named Data-4 and Data2-6.

These Storage pools have the Luns from the 3rd expansion chassis in them, D8, D9 and AS3.

When viewing the volume in XSan Admin, these two newly created Storage Pools show up, then disappear. They show up, and disappear, about every 30 seconds.

My question is: How can I remove those two Storage Pools that mysteriously appeared, so those LUNS will be unused again, and I can add them to the proper Storage Pools? (or at least try to)

There is no data on these mysterious storage pools, and the space does not show up as added to the volume, although the storage pools sometimes show up under the volume.

Any help will be appreciated. - I have not done much with the xsan command line tools...but am willing.

Here are some Pics to illustrate the setup:






Thanks,

Bob

[macrobatix]

If anyone is interested, I solved this problem by using cvlabel to unlabel the luns, then manually opening the volume cfg file on each metadata controller and removed all references to the luns, and the odd storage affinities.

Restarted all metadata controllers, and the luns showed up as available.

Added them to existing storage affinities with success this time.

Ran fsck on the volume and now all is working properly.