Q: Problems with LUN's after they became self unlabeled

Hello

Yesterday my customer call me and says, the Xsan crash and volume is not accessible. When i arrive i see the LUN's is not visible but Xsan Admin and don't appear in Disk Utility as Xsan Component. I have only 2 LUN's - one for metadata and second for data. I use 12 disks Infortrend EonStor DS - 10 disk RAID5 for data and 2 disks RAID1 for metadata.
I also see in Disk Utility the lun with Data have also seen this http://macfan.pl/acd30/luns.jpg
After a few hours of strugglin i discover the problems is with name of the LUN's
So i make a backup of visible luns using command cvlabel -c >oldcvlabel
and then edit and apply the names found in Volume.cfg
When i apply labelist i see there is some issues with size of LUN with metadata. What could go wrong? When i try to start volume i get this
*[0218 20:39:04] 0x7fff702ddca0 (Info) Server Revision 3.5.0 Build 7443 Branch branches_35X (412.3)*
*[0218 20:39:04] 0x7fff702ddca0 (Info) Built for Darwin 10.0 i386*
*[0218 20:39:04] 0x7fff702ddca0 (Info) Created on Mon Dec 7 12:52:39 PST 2009*
*[0218 20:39:04] 0x7fff702ddca0 (Info) Built in /SourceCache/XsanFS/XsanFS-412.3*
*[0218 20:39:04] 0x7fff702ddca0 (Info)*
Configuration:
* DiskTypes-2*
* Disks-2*
* StripeGroups-2*
* MaxConnections-139*
* ThreadPoolSize-256*
* StripeAlignSize-8*
* FsBlockSize-131072*
* BufferCacheSize-32M*
* InodeCacheSize-8192*
* RestoreJournal-Disabled*
* RestoreJournalDir-None*
*[0218 20:39:04] 0x7fff702ddca0 (*Error*) Configured size of 3900053471 for disk "Xsan1" in stripe group 0 exceeds labeled capacity 3899937352*
*[0218 20:39:04] 0x7fff702ddca0 (*FATAL*) Cannot open stripe group "MetadataAndJournal" - Invalid argument*
*Logger_thread: sleeps/1 signals/0 flushes/1 writes/1 switches 0*
*Logger_thread: logged/7 clean/7 toss/0 signalled/0 toss_message/0*
*Logger_thread: waited/0 awakened/0*


Here is my Volume.cfg

*# ***************************************************************************
*# A global section for defining file system-wide parameters.*
*# ***************************************************************************
*FileLocks Yes*
*GlobalSuperUser Yes*
*Quotas Yes*
*WindowsSecurity No*
*EnforceACLs Yes*
*EnableSpotlight No*
*NamedStreams Yes*
*ForceStripeAlignment Yes*
*UnixIdFabricationOnWindows Yes*
*Debug 0*
*AllocationStrategy Round*
*SpotlightSearchLevel ReadWrite*
*InodeExpandMin 8*
*InodeExpandInc 32*
*InodeExpandMax 2048*
*BufferCacheSize 32M*
*JournalSize 128M*
*FsBlockSize 128K*
*InodeCacheSize 8K*
*MaxConnections 139*
*MaxLogSize 10M*
*ThreadPoolSize 256*
*UnixNobodyUidOnWindows -2*
*UnixNobodyGidOnWindows -2*


*# ***************************************************************************
*# A disktype section for defining disk hardware parameters.*
*# ***************************************************************************

*[DiskType "Xsan1Type"]*
*Sectors 3900053471*
*SectorSize 512*

*[DiskType "Xsan2Type"]*
*Sectors 35151828959*
*SectorSize 512*


*# ***************************************************************************
*# A disk section for defining disks in the hardware configuration.*
*# ***************************************************************************

*[Disk "Xsan1"]*
*Status Up*
*Type "Xsan1Type"*

*[Disk "Xsan2"]*
*Status Up*
*Type "Xsan2Type"*


*# ***************************************************************************
*# A stripe section for defining stripe groups.*
*# ***************************************************************************

*[StripeGroup "MetadataAndJournal"]*
*Status Up*
*Exclusive Yes*
*Metadata Yes*
*Journal Yes*
*Read Enabled*
*Write Enabled*
*MultiPathMethod Rotate*
*StripeBreadth 8*
*Node "Xsan1" 0*

*[StripeGroup "Data"]*
*Status Up*
*Exclusive No*
*Metadata No*
*Journal No*
*Affinity "Data"*
*Read Enabled*
*Write Enabled*
*MultiPathMethod Rotate*
*StripeBreadth 8*
*Node "Xsan2" 0*



And here is my labelist before relabeling (but after self unlabeling)
*CvfsDisk_UNKNOWN /dev/rdisk1 # host 2 lun 0 sectors 3900053471 sector_size 512 inquiry [IFT DS S12F-G1440 385C] serial 600D02310009A2B8640AF2A800993DF0*
*CvfsDisk_UNKNOWN /dev/rdisk2 # host 2 lun 1 sectors 35151828959 sector_size 512 inquiry [IFT DS S12F-G1440 385C] serial 600D02310009A2B8063CAD77421038F9*


and after relabeling
*Xsan1 /dev/rdisk1 # host 2 lun 0 sectors 3900053471 sector_size 512 inquiry [IFT DS S12F-G1440 385C] serial 600D02310009A2B8640AF2A800993DF0*
*Xsan2 /dev/rdisk2 # host 2 lun 1 sectors 35151828959 sector_size 512 inquiry [IFT DS S12F-G1440 385C] serial 600D02310009A2B8063CAD77421038F9*


What can i do to start volume correctly and dont loose the data on it?
Is this a normal situation that the lun can itself change the name?

Thanks in advance