Increase the Swap Partition in Operations Manager

Document created by umar.adams Expert on Aug 19, 2015Last modified by don.hovey on Nov 3, 2016
Version 3Show Document
  • View in full screen mode

To extend your Operations Manager Swap space, follow the steps below:

 

  1. Login to your Operations Manager instance via cli and issue the following command to shutdown your instance "shutdown now"
  2. Once the appliance is powered down, extend the attached hard disk by the amount of "swap space" you would like to add using the recommended, documented, methods for the hypervisor in use (VMWare vCenter, XenServer or RHEV). if you want to add 20GB of swap, increase the vm's hard disk by 20GB
    • IMPORTANT NOTE:  If you are using vCenter and cannot resize the disk because the option is grayed out, this likely means you have a snapshot on the Operations Manager appliance.  VMWare will not permit you to resize the VMDK if a snapshot is present, therefore you can either delete all snapshots for the VM, or, you can clone a new appliance from the existing one (which will have no snapshots) and extend/resize the disk on the clone and use this VM going forward.
  3. Power up the appliance again.  Once booted, log back into the console using the root account.  Confirm that the additional space is visible to the appliance by running ‘fdisk –l’.  The indicated capacity for device /dev/sda should now be greater than 20GB, for example a disk extended to 30GB will look like this:

    Disk /dev/sda: 32.2 GB, 32212254720 bytes
    255 heads, 63 sectors/track, 5221 cylinders, total 83886080 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0x167942c0

    However, the root file system will still report its capacity as 20GB:
    Disk /dev/mapper/systemVG-LVRoot: 19.1 GB, 19113443328 bytes
    255 heads, 63 sectors/track, 2323 cylinders, total 37330944 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
  4. Issue the command 'yast' on the appliance console.
  5. Using the tab key to navigate the windows, select System on the left pane, and Partitioner on the right pane and hit enter.
    Screenshot_6_4_13_2_13_PM.jpg
  6. Select 'Yes' at the warning and hit enter.
  7. Select Hard Disks on the left pane, hit enter, and then select Add Partition on the right pane.
    Screenshot_6_4_13_2_17_PM.jpg
  8. Select Primary Partition as the partition type and select Next.
    Screenshot_6_4_13_2_22_PM.jpg
  9. Select Maximum Size, then select Next
    Screenshot_6_4_13_2_23_PM.jpg
  10. Select Do not format partition, and assign the partition the file system ID 0x8E Linux LVM.  Select Do not mount partition, then select Finish
    Screenshot_6_4_13_2_26_PM.jpg
  11. We will now need to resize the system volume group to make use of the new partition we just created.  Once back in the main Partitioner window, select Volume Management on the left pane, select /dev/systemVG on the right pane, select Resize and hit enter.
    Screenshot_6_4_13_2_29_PM.jpg
  12. Select Add All in between the left and right panes and hit enter to move /dev/sda3 to the Selected Physical Volumes list.
    Screenshot_6_4_13_2_35_PM.jpg
  13. Select Finish and hit enter
    Screenshot_6_4_13_2_36_PM.jpg
  14. Once back to the main Partitioner window, select /dev/systemVG/LVSwap on the right pane, select Resize and hit enterStep_14.png
  15. Select Maximum Size, select OK and hit enter to apply the setting.
  16. Select Next and hit enter.

Screenshot_6_4_13_2_43_PM.jpg

18. Select Finish and hit enter.

Screenshot_6_4_13_2_44_PM.jpg

19. Once the changes are completed, select Quit and hit enter to exit the YaST utility and be returned back to the command line.

20. Reboot the appliance by issuing the command 'shutdown -r now' to ensure that all the above changes are applied.

21. Run the command ‘swapon -s’ to confirm that the swap partition has now been extended to consume the additional space which was allocated.

Attachments

    Outcomes