Device Size

After you create the ES GuardPoint on the device, the device size reported to applications is the size of the device minus the space reserved for the CTE Private Region. This can lead to a discrepancy between the disk size reported by some applications versus the size reported by system utilities such as fdisk.

Do not shrink ES GuardPoints. Due to relocation of user data from CTE Private Region, if you shrink the device, you may corrupt data on the device.

The ES Header contains both the available device size and the size of the CTE Private Region. To view the ES Header, use the voradmin esg status <device-name> command. The Exported Disk Size field shows the disk size available for use by other applications. The Private Region Size field shows the disk size reserved for CTE. For example:

 voradmin esg status /dev/sdh
ESG Header on /dev/secvm/dev/sdh
    Version:                1
    Change:                 0
    Notifications:          None
    Storage Status:         None
        Private Region Size:    129024 sectors
        Exported Device Size:   20842496 sectors
    Key UUID:               2c3ee4af-010c-3593-898e-f2f62d29222d
    Mount Path:             None

The voradmin esg status command also reports the UUID of the XTS-AES 256 key applied to the device. The reported UUID matches the UUID of the key as shown on the CipherTrust Manager key property and KMIP key object.