Unsolved
This post is more than 5 years old
13 Posts
0
1121
November 21st, 2014 06:00
Why can't the max capacity of an expanded LUN be utilised?
Working on a Clariion CX4-120 running Flare 30. Standard RAID Group LUN used as an RDM by VMware.
Our Admins have expanded a 120gb LUN by 60gb and using the expansion wizard. They specified the Concatenate option but could not then specify the Max size of 180gb to be used. This option was greyed out along with the option to specify a custom capacity.
The wizard completed successfully and does show the Max capacity of 180gb, but with a user capacity of 120gb. LUN properties show the same thing.
They have tried using the properties window of the LUN to alter its capacity but again the Max and Other options are greyed out.
Any ideas as to what has gone wrong and how to allow the servers to see the maximum capacity?
Thanks in advance
dynamox
9 Legend
•
20.4K Posts
0
November 21st, 2014 07:00
have you tried naviseccli to rule out Navisphere UI issues ?
dynamox
9 Legend
•
20.4K Posts
1
November 21st, 2014 10:00
take a look at the admin guide for more options, i am thinking something around
metalun -expand -lus LUN# -cap 60 -sq gb
if 60 does not work, try 59
SunshineGirl1
13 Posts
0
November 21st, 2014 10:00
Not as yet; would you suggest some useful commands?
SunshineGirl1
13 Posts
0
November 21st, 2014 11:00
Thanks, will give that a go.
Raj10
37 Posts
2
November 22nd, 2014 10:00
It seems the metalun got expanded, but usable capacity not showing the expected size, possibly due to layered driver sitting on top of the lun.
Can you provide more information whether the lun is being used for any replication purpose like mirrorview, clone etc.
Please run the below command using the NAVICLI to check the layered driver sitting on it.
naviseccli -h -user -password -scope 0 getlun -messner -stack
If it shows driver sitting on it like K10Faradmin, then it is mirror view driver which is stopping to display the expanded size. In that case, you need to follow below steps.
1) Fracture the mirror.
2) Remove the secondary image.
3) Destroy the primary image/mirror. (Destroying the primary image/mirror doesn't mean deleting the primary LUN.)
4) Expand both the LUNs (primary image and secondary image) both should be same size. Choose "Maximum Capacity" under the lun properties.
5) Recreate the mirror and start fresh.
Note : It will be a full sync for the first time when you establish mirror relationship again.
Even after deleting the mirrors, if the option to choose "Maximum Capacity" is grayed out, then run below commands before you do steps 4 and 5 as mentioned above.
naviseccli -h -user -password -scope 0 mirror -async|-sync -setfeature - off -LUN
Let us know how it goes.
SunshineGirl1
13 Posts
0
November 27th, 2014 06:00
The LUN is replicated so that looks like it could be the issue. I've passed this over to the admins, so watch this space .
Thanks for your help.