Hey guys, I want to sandbox a vm for performance testing. It is on lun 10, I want to remove the lun and assign it only to a stand alone esx server.
Should I remove the lun from the san fabric only and then attach it to the stand a lone esx.
or
Should I remove the lun from with in virtual center, then from the san fabric and then reattach it?
Respectfully,
Matthew
Kaizen!
Clumsy but working: If you want to find out if anything on an ESX node is using a LUN, you could do this:
ls -lh /vmfs/volumes
This should return something like:
TEST-LUN -> 4761ad54-a9d7a210-7d51-001b210501b8
Note the UUID of the LUN (the long number) and copy that. Now do this:
ps -efww | grep <that long number>
It should return any process using that LUN. You would have to do that on each host connected to that LUN to be sure. There's got to be an easier way... But annot think of one.
this will see the LUNs without attaching it to the ESX
Thanks Erik.
I will try this next time I need te remove a lun.
Doing this on all hosts is no problem for me, since I've got some scripts using plink.exe for that.
Arnim van Lieshout
Visit my blog at: http://www.van-lieshout.com
donaldmickey, I still do not understand what you are getting at. "see" the LUN without attaching? Seeing it on what?
Resignaturing will resignature ALL LUNs visible to that ESX node, which is a big risk. Apart from that, it does not help to get anything usefull done. Just a rescan is enough to get the (now zoned) LUN visible. Resignaturing is NOT needed.
Visit my blog at http://erikzandboer.wordpress.com
I agree with Erik.
When you put a new host in a cluster you don't have to resignature either.
Arnim van Lieshout
Visit my blog at: http://www.van-lieshout.com
Hey Donald,
Let me change your order of operations there just a bit.
Add the lun to the new stand alone esx FIRST, BEFORE removing it from the other ESX servers.
This will ensure that you can still work with the lun if the stand alone refuses to see the new lun.
Respectfully,
Matthew
Kaizen!