Cleaning up the mapped RDM LUNs in the guest operating system and ESX server

You must clean up the RDM LUNs in the guest operating system as well as in ESX server.

Cleaning up the mapped RDM LUNs in the guest operating system

The following steps must be done in the guest operating system.

Steps

  1. From the vCenter navigation pane, select the Virtual Machine in which the RDM mapping is done.

  2. Right-click the virtual machine and turn off your guest operating system.

  3. Right-click the virtual machine and select Edit settings.

    The virtual machine properties dialog box appears.

  4. In the virtual machine properties dialog box, select the Hardware tab.

    You will find the entire RDM mapped entry as Mapped RAW LUN for every RDM entry.

  5. Select the RDM mapped entry and click Remove.

    The Removal Options appears in the right pane.

  6. In the Removal Options, select Remove from virtual machine and delete files from disk.

  7. Click OK.

    All the RDM mapped entries are removed from the guest operating system.

    After you remove RDM LUN entries from the guest operating system, you need to remove them from the ESX server.

Cleaning up the mapped RDM LUNs in the ESX server

The following steps must be done only by the ESX server administrator for a complete cleaning up of all RDM LUN entries in the ESX server.

Turn off your virtual machine before working on the virtual machine directory.

Steps

  1. Go to the virtual machine directory.

  2. Change to the directory cd /vmfs/volumes/Data store path.

    # ls -l
total 1024
drwxr-xr-t 1 root root 1540 Apr 19 23:54 4bc702de-fa7ec190-992b-001a6496f353
lrwxr-xr-x 1 root root   35 May 11 07:56 local_storage (1) -> 4bc702de-fa7ec190-992b-001a6496f353

    All the files and directories are listed here.

  3. Select the appropriate data store in which the virtual machines resides.

  4. Change the directory to data store.

    The virtual machine directory is displayed here.

  5. Change the directory to virtual machine in which you want to clean up RDM LUN mapping.

    All the files are listed in the virtual machine directory.

  6. Delete all vmdk files, which have SMVI string embedded. Alternatively, you can also identify the vmdk file using LUN name.

    Alternatively, you can also identify the vmdk file using LUN name.

    If you have a vmdk file of the LUN name as rdm1, delete only rhel4u8-141-232_SMVI_vol_esx3u5_rdm1-rdmp.vmdk and rhel4u8-141-232_SMVI_vol_esx3u5_rdm1.vmdk files.

    Delete vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4XzK2HT_22-rdmp.vmdk and vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4XzK2HT_22.vmdk vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4YG4NuD_53-rdmp.vmdk files.

  7. Remove the vmdk file entries from the virtual machine configuration file (vmx) as well.

    The following is an example of removing vmdk file entries from the vmx file.

    Name Description

    rhel4u8-141-232

    Name of the virtual machine

    SMVI

    Indicates that this vmdk file is created by SnapManager for Virtual Infrastructure server

    vol_esx3u5

    Name of the volume where the LUN is created

    rdm1

    Name of the LUN

    rdmp

    Signifies that this is physically compatible RDM LUN

    vmdk

    Virtual Machine Disk File

    		 
    [root@ rhel4u8-141-232]# vi rhel4u8-141-232.vmx
		:
		:
scsi3:1.fileName = "rhel4u8-141-232_SMVI__vol_esx3u5_rdm1.vmdk"
scsi3:1.mode = "independent-persistent"
scsi3:1.ctkEnabled = "FALSE"
scsi3:1.deviceType = "scsi-hardDisk"
scsi3:1.present = "TRUE"
scsi3:1.redo = ""

  8. Delete the entries as specified in the preceding example, including quotes and commas except for the scsi3:1.present entry, which you should change to FALSE from TRUE.

  9. Save and quit the file.

  10. Turn on the virtual machine.