2.9.1.1 Extending the root LVM Partition on Systems Running Oracle Exadata System Software Release 11.2.3.2.1 or Later

The following procedure describes how to extend the size of the root (/) partition on systems running Oracle Exadata System Software release 11.2.3.2.1 or later:

Note:

  • This procedure does not require an outage on the server.

  • For management domain systems, the active and inactive Sys LVM's are LVDbSys2 and LVDbSys3 instead of LVDbSys1 and LVDbSys2.

  • Make sure that LVDbSys1 and LVDbSys2 are sized the same.

  1. Collect information about the current environment.
    1. Use the df command to identify the amount of free and used space in the root partition (/).
      # df -h /
      

      The following is an example of the output from the command:

      Filesystem                    Size  Used Avail Use% Mounted on
      /dev/mapper/VGExaDb-LVDbSys1   30G   22G  6.2G  79% / 
      

      Note:

      The active root partition may be either LVDbSys1 or LVDbSys2, depending on previous maintenance activities.

    2. Use the lvs command to display the current volume configuration.
      # lvs -o lv_name,lv_path,vg_name,lv_size
      

      The following is an example of the output from the command:

      LV                 Path                            VG       LSize
      LVDbOra1           /dev/VGExaDb/LVDbOra1           VGExaDb  100.00g
      LVDbSwap1          /dev/VGExaDb/LVDbSwap1          VGExaDb  24.00g
      LVDbSys1           /dev/VGExaDb/LVDbSys1           VGExaDb  30.00g
      LVDbSys2           /dev/VGExaDb/LVDbSys2           VGExaDb  30.00g
      LVDoNotRemoveOrUse /dev/VGExaDb/LVDoNotRemoveOrUse VGExaDb  1.00g
      
  2. Use the df command to identify the file system type that is used in the root partition (/).
    # df -hT /
    

    The following is an example of the output from the command:

    Filesystem                    Type  Size  Used Avail Use% Mounted on
    /dev/mapper/VGExaDb-LVDbSys1  ext3   30G   22G  6.2G  79% / 
    

    In this example, the file system type is ext3.

  3. If the file system type is not xfs, use the following tune2fs command to check the online resize option. If the file system type is xfs, then you can skip this step.
    tune2fs -l /dev/mapper/vg_name-lv_name | grep resize_inode
    

    For example:

    tune2fs -l /dev/mapper/VGExaDb-LVDbSys1 | grep resize_inode
    

    The resize_inode option should be listed in the output from the command. If the option is not listed, then the file system must be unmounted before resizing the partition. Refer to Extending the root LVM Partition on Systems Running Oracle Exadata System Software Earlier than Release 11.2.3.2.1 to resize the partition.

  4. Verify there is available space in the volume group VGExaDb using the vgdisplay command.
    # vgdisplay -s
    

    The following is an example of the output from the command:

    "VGExaDb" 834.89 GB [184.00 GB used / 650.89 GB free]
    

    The volume group must contain enough free space to increase the size of both system partitions, and maintain at least 1 GB of free space for the LVM snapshot created by the dbnodeupdate.sh utility during upgrade.

    If there is not enough free space, then verify that the reclaimdisks.sh utility has been run. If the utility has not been run, then use the following command to reclaim disk space:

    # /opt/oracle.SupportTools/reclaimdisks.sh -free -reclaim 
    

    If the utility has been run and there is not enough free space, then the LVM cannot be resized.

    Note:

    reclaimdisks.sh cannot run at the same time as a RAID rebuild (that is, a disk replacement or expansion). Wait until the RAID rebuild is complete, then run reclaimdisks.sh.

  5. Resize both LVDbSys1 and LVDbSys2 logical volumes using the lvextend command.

    In the following example, XG is the amount of space in GB that the logical volume will be extended. The amount of space added to each system partition must be the same.

    # lvextend -L +XG --verbose /dev/VGExaDb/LVDbSys1
    # lvextend -L +XG --verbose /dev/VGExaDb/LVDbSys2
    

    The following example extends the logical volumes by 10 GB:

    # lvextend -L +10G /dev/VGExaDb/LVDbSys1
    # lvextend -L +10G /dev/VGExaDb/LVDbSys2
    
  6. Resize the file system within the logical volume.
    • For ext3 and ext4 file system types, use the resize2fs command:

      # resize2fs /dev/VGExaDb/LVDbSys1
      # resize2fs /dev/VGExaDb/LVDbSys2
      
    • For the xfs file system type:

      1. Use the xfs_growfs command to resize the active file system:

        # xfs_growfs /
      2. Determine the inactive root partition.

        The inactive root partition is LVDbSys1 or LVDbSys2, whichever is not currently mounted.

        Examine the output from the df command to confirm the active partition. For example:

        # df -hT /
        Filesystem                    Size  Used Avail Use% Mounted on
        /dev/mapper/VGExaDb-LVDbSys1   30G   22G  6.2G  79% / 
        

        The example shows LVDbSys1 as the active partition. Therefore, the inactive partition is LVDbSys2.

      3. Mount the inactive root partition to a temporary location.

        For example:

        # mkdir -p /tmp/mnt/root
        # mount -t xfs /dev/VGExaDb/LVDbSys2 /tmp/mnt/root
      4. Use the xfs_growfs command to resize the inactive file system:

        # xfs_growfs /tmp/mnt/root
      5. Unmount the inactive root partition.

        For example:

        # umount /tmp/mnt/root
  7. Verify the space was extended for the active system partition using the df command.
    # df -h /