unused LUNs duplicate LUNs

Andrew Allen's picture

Xsan 3.1 created two duplicate LUNs

HI,

We've got a system with 3 different SANs on it. We added the third SAN a few weeks ago and finally got it working. The third SAN (SAN3) has three LUNs which I defined in the Infortrend web interface for the RAID box. LUN names are FSN_SAN3_LUN1, FSN_SAN3_LUN2 and FSN_SAN3_LUN3.

LUN1 is a  RAID 1 for the Xsan metadata and journaling parition that covers two drives.

LUN2 is a RAID6 over 11 drives for 36 TB total and I'm using it for video

LUN3 is another RAID6 over 11 drives for 36TB total and I'm using it for video.

My first question, now that I think of it, is this: how bad is it to use 2 LUNs for video data in Xsan instead of the 4 LUNs it askes for? SAN1 has 4 luns for video data, but SAN2 was made with just 2 LUNs and it's been in use with video data for 4 years straight with no failures. Are there issues with ignoring/being ignorant of Xsan's preference of 4 LUNs for video data?

My second question (the subject of the thread) is this: We've been using SAN3 for about a week now. Editors have already bumped 25TB worth of stuff on it and it functions fine. However, for some reason Xsan Admin is reporting that there are duplicate lun names for this volume. Here's what the Console is spitting at me ~every 50 seconds:

Xsan Admin: ERROR : Error getting list of volumes: kOfflineError (0)
Xsan Admin: ERROR : Error getting list of volumes: kOfflineError (0)
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN2
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN3
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN2
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN3
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN2
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN3
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN2
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN3
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN2
Xsan Admin: ERROR: Duplicate LUN label: FSN_SAN3_LUN3

Sometimes it will include 1-3 more messages for " kOfflineError (0)"

When I go into the LUN section of Xsan Admin on the left, there are indeed 2 duplicate LUNs with these names. FSN_SAN3_LUN2 and FSN_SAN3_LUN3 appear twice in the list. One of the FSAN_SAN3_LUN2 entries has a yellow exclamation mark over it and is flagged under Errors & Warnings. It is correctly listed as a Video Storage Pool and as part of the Volume FSN_SAN3. The other entry for LUN2 has no error flag, and has nothing populating the "Storage Pool" and "Volume" column fields. Both are listed as being 36TB in size. 

The exact same scenario is the case for FSN_SAN3_LUN3.

The entries for LUN2 and LUN3 that do NOT have data in the Storage and Volume column fields appear in the "Unused LUNs" tab.

My questions are: A) where did these come from and B) can I delete them? If yes for B), how? Can I just Right Click > Remove LUN Label? Is that a problematic action? Can I do that while the SANs are running without messing something up?

Probably a simple question, but I don't want to muck anything up. I'm still very new to Xsan. Did Xsan create these LUNs to try to fulfill it's want for making 4 LUNs for Video paritions? I shouldn't think so because I SAN2 has the same LUN formating (LUN1 for MetadataAndJournaling and then LUN2 and LUN3 as equal size (18TB) Video Storage Pools). 

Subscribe to RSS - unused LUNs duplicate LUNs