cancel
Showing results for 
Search instead for 
Did you mean: 

luns on FC60

Vamsidin
Frequent Advisor

luns on FC60

Hi Gurus,
I have created a Lun in an FC60 which is showing the lun id as 1.But I already have a lun1. Now the issue is that the lunid's are conflicting as they have two lun's with the same id.
So I would like to delete one lun without affecting the other.

If I isseu the command amcfg -D I do not want both the luns to get deleted.

Is there a way I can do it

thank you
3 REPLIES
Crewescontrol
Frequent Advisor

Re: luns on FC60

Hi,

Could you post the amdsp -a


Cheers
Vamsidin
Frequent Advisor

Re: luns on FC60

Attached is the output of the â amdsp â aâ with controller and LUN information you require. You can see from the file that we have a curious problem.



Firstly you will notice that the array reports the overall status as â READYâ , however if you look at the list of available LUNS all are marked as optimal but the disks associated with LUN5 canâ t be identified



-----------------------------------------

LUN Status Capacity Ctrl RAID Segment Disks

--- ----------------- --------- ---- ---- ------- -----

0 OPTIMAL 101.5 GB B 5 16 1:0

2:0

3:0

4:0

5:0

1:9

2:1

1 OPTIMAL 16.9 GB B 1 4 1:8

2:8

2 OPTIMAL 16.9 GB B 1 4 3:8

4:8

3 OPTIMAL 16.9 GB B 1 16 3:1

4:1

4 OPTIMAL 33.8 GB B 1 16 2:9

3:9

4:9

5:9

5 OPTIMAL 16.9 GB B 1 16 Can't identify

6 OPTIMAL 68.3 GB B 1 16 1:1

5:1

31 UTM:GOOD





When you then examine the disk output (amdsp â d - below) you will notice that the disks 5:1 and 1:1 indicate they are 17GB in size however in the above output the array says these disks are LUN 6 with a size of 68GB, in fact they are in LUN5. LUN5 is actually in use with disk 1:1 and 5:1 we know this because when we created this LUN with those disks first, we then later added in LUN 6 using the disks 2:2 and 5:2 (68GB), although LUN 6 size is correct it seems to think the disks in slot 5:1 and 1:1 are associated with this LUN (when they are not).





SCSI Channel:ID = 5:1

Enclosure = 4

Slot (0-based) = 2

Disk State = OPTIMAL

Disk Group and Type = 093C48001047A0989A LUN

Capacity = 17.0 GB

Manufacturer and Model = SEAGATE ST318404LC

Serial Number = 3BT1ZC81

Firmware Revision = HP04



SCSI Channel:ID = 1:1

Enclosure = 0

Slot (0-based) = 2

Disk State = OPTIMAL

Disk Group and Type = 093C48001047A0989A LUN

Capacity = 17.0 GB

Manufacturer and Model = SEAGATE ST318404LC

Serial Number = 3BT1Y3Z5

Firmware Revision = HP04



Now if you look at the disk groups (amdsp â g) you will see that 2 of the groups (LUN 5 and 6) share the same LUN id (bad).



Disk Group 093C48001047A0989A:

Disk Group Type = LUN

Number of LUNs = 1

LUN(s) = 6

Remaining Capacity = 0.0 MB

RAID Level = 1

Segment Size = 16 KB

Disks:

1:1 5:1

Disk Group 093C48001247A9ADD4:

Disk Group Type = LUN

Number of LUNs = 1

LUN(s) = 6

Remaining Capacity = 0.0 MB

RAID Level = 1

Segment Size = 0 KB

Disks:

2:2 5:2
One of the LUNS has data on it and therefore we canâ t take the risk of simply deleting the LUN with no data on it as it seems to be associated (linked) with the LUN that has data. It seems to be that there is some corruption in the array.

Vamsidin
Frequent Advisor

Re: luns on FC60

thank you... issue4 was with lun 0