Professional Documents
Culture Documents
What is the correct procedure to remove a LUN which is no longer required? Setup is a Solaris 10 server, dual pathed FC to EMC storage and managed with VxVM 5.1. Once the LUN has been removed from Veritas (removed from DG then vxdisk rm <disk>) At what point can I unmask the LUN on the storage side? Is it before or after I remove the disk with powermt? Do I even perform a powermt remove? Once that is done, I would then remove from OS via cfgadm, then devfsadm. What I am currently trying to do a powermt remove <emcpower#> after I do a vxdisk rm <emcpower#>, but it complains that the device is still in use.
somebox01:# /etc/powermt remove dev=emcpower123a Cannot remove device that is in use: emcpower123a somebox01:#
Thoughts appreciated. Pete Filed under: Storage Foundation, Solaris, Storage and Clustering 0 (0 Votes)
y y
as you are saying that you are getting above mentioned error, just wanted to confirm if you have removed the device from vxvm using step 2 above ? Can you also confirm the vxvm version you are using ?
Gaurav PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided. +1 (3 Votes)
y
5. unconfigure device from OS (cfgadm/luxadm depending on age of platform. For Solaris 10 cfgadm should work. also run devfsadm -Cv after disks have been unpresented from storage) Pete, It sounds like it's possible that vxesd may have picked up the devices again after you removed them with vxdisk rm. Try stopping vxesd, removing the disks with vxdisk rm (and removing the dmp devices), then try the powermt remove again. The fact that there is/was a private region on the disk should not impact the removal if the disk has been removed cleanly from VxVM/DMP (ie: and not picked up again by vxesd) regards, Grace If this post has helped you, please vote or mark as solution 0 (0 Votes)
y
What ive done in the past (non powerpath) is just remove disk from VxVM, remove the disk from the SAN, then uncofigure the device (cfgadm -o unusable_FCP_dev -c unconfigure c:....) , then devfsadm. I've never done anything with DMP, or luxadm when removing a LUN. vxvm is 5.1
Thank you.
0 (0 Votes)
y
Gaurav PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided. +1 (1 Vote)
y
4. At this point you should be able to remove the disk with " cfgadm" if the disk is in unusable state. If its in 'failing' state use 'luxadm' to offline the disk. You cannot unconfigure a disk unless it is in 'unusable' state and you have to unconfigure both the paths of your disk. If your disk is "c2t5006048ad52f4106d37" then #cfgadm -al -o show_SCSI_LUN |grep <disk>
#luxadm -e offline /dev/dsk/<device> #cfgadm -c unconfigure -o unusable_SCSI_LUN c2::5006048as52f4106 #cfgadm -c unconfigure -o unusable_SCSI_LUN c4::5006048as52f4109 4. devfsadm
Nandini
+1 (1 Vote)
y
Hi Pete, you are right, you will not be able to do a vxdiskunsetup after doing a vxdisk rm, the order of steps should be reversed. vxdisk rm will not be cleaning the private region from the disk however vxdiskunsetup will. So you need to run vxdiskunsetup first followed by vxdisk rm.
Gaurav PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided. 0 (0 Votes)
y
Gaurav PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.