How To Do Custom Partitioning Of Disks On Compute Nodes In Exalogic Physical Environment
(Doc ID 1489962.1)
Last updated on NOVEMBER 28, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.0 and later
This document provides procedure for custom partitioning of the disk on Exalogic Compute nodes in Exalogic Physical Environments running with Exalogic Elastic Cloud Software (EECS) versions 1.0.0.x.x & 2.0.0.x.x. The procedure involves reconfiguration of the disk logical volumes to relocate directories such as opt, usr, and var in the default root file system to their own logical volumes, and can be extended and customized to other directories as required. This procedure is not applicable to Exalogic virtual environments.
The target audience for this document are system administrators who are responsible for performing disk and file system management of compute nodes in an Exalogic Physical configuration.
In default Exalogic Physical Environments running with EECS versions 1.0.0.x.x & 2.0.x.x.x, the available space in the RAID-controlled SSDs is partitioned as shown below.
The entire root file system is located in a single logical volume (LogVol00). On 32 GB SSDs, the logical volume occupies approximately 15 GB, while on newer 100 GB SSDs, the logical volume size is approximately 85 GB. The remaining space on disk is allocated to a logical volume for swap space (LogVol01) and a small boot partition (/dev/sda1).
Custom partitioning of disk may be required to align with corporate IT policies on disk management. Customers may also want to limit the amount of space allocated to individual directories such as opt, usr, and var in the root file system to prevent files under a specific directory from consuming all available space in the root partition. Configuring multiple logical volumes, one for each directory as required, also adds flexibility for targeted expansion and backup.
The procedure described in this document creates new logical volumes for opt, usr, and var directories, and may be extended to other directories as required. The example sizes of the logical volumes in the procedure are for 32 GB SSDs; for newer 100 GB disks, you may choose larger sizes. Also, you may choose the actual sizes of the custom logical volumes based on your requirements and any existing policies.
The process of reimaging the compute node using the EECS ISO or PXE server will NOT preserve custom partitions. If the compute node is reimaged after custom partitioning is performed as described in this document, the partitioning procedure will need to be redone.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document