After destroying a XSAN Volume and recreating the underlying arrays and generating new LUNs, several of the old, now non-existent LUNs, are still showing up in XSAN admin, with yellow warning flags. I have repaired the LUN Map on the XServe RAID, rebooted all RAID controllers, tried unlabeling them in Xsan Admin...To no avail, they are stuck there. I have since recreated a volume with the new LUNs and all is working perfectly, except that these annoying old LUNs are stuck in the admin console. When I do a cvlabel -l, these LUNs do not appear at all. So this seems to be merely a glitch with the admin console. It does not impact performance, but I would really prefer to get rid of them if I could...
I am running XSAN 2.2 on an XSERVE MDC running 10.6.4 server. Fibre Channel fabric is run using 2 stacked QLogic SanBox 1400 units, all clients (3) also running XSAN 2.2 on 10.6.4. Storage is provided by one XServe RAID system as well as a brand new Promise VTRAK. I tried several configurations, ended up changing the RAID array setup several times, and now I have 3 old LUNs from the XRAID system and one old LUN from the VTRAK still showing up in XSAN Admin.
