Exadata Database Compute Node Volume Is Smaller Than Expected

Asset ID:	1-72-1525286.1
Update Date:	2013-02-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1525286.1 : Exadata Database Compute Node Volume Is Smaller Than Expected

Applies to:

Exadata X3-2 Half Rack - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

The standard size of VGExaDb volume group is much smaller and has less free space then same standard VDG group:

root@ptqaxdb0101c ~]# vgdisplay
--- Volume group ---
VG Name VGExaDb
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 277.96 GB
PE Size 4.00 MB
Total PE 71158
Alloc PE / Size 47104 / 184.00 GB
Free PE / Size 24054 / 93.96 GB ->>> This free space seems small

[root@ptqaxdb0104c ~]# /opt/oracle.SupportTools/reclaimdisks.sh -check
[INFO] This is SUN FIRE X4170 M3 machine
[INFO] Number of LSI controllers: 1
[INFO] Physical disks found: 4 (252:0 252:1 252:2 252:3)
[INFO] Logical drives found: 1
[INFO] Dual boot installation: no
[INFO] Linux logical drive: 0
[INFO] RAID Level for the Linux logical drive: 5
[INFO] Physical disks in the Linux logical drive: 4 (252:0 252:1 252:2 252:3)
[INFO] Dedicated Hot Spares for the Linux logical drive: 0
[INFO] Global Hot Spares: 0
[INFO] Valid single boot configuration found for Linux: RAID5 from 4 disks with no global and dedicated hot spare disks

[root@ptqaxdb0104c ~]# /opt/MegaRAID/MegaCli/MegaCli64 -LDInfo -Lall -Aall

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name :DBSYS
RAID Level : Primary-5, Secondary-0, RAID Level Qualifier-3
Size : 835.394 GB
Parity Size : 278.464 GB
State : Optimal
Strip Size : 1.0 MB
Number Of Drives : 4
Span Depth : 1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy : Disabled
Encryption Type : None
Is VD Cached: No

Changes

We can see the reclaimed space reflected in the total space available, but the extra free space is not visible in vgdisplay.

Cause

The volume group should have two disks, but reviewing vgdisplay command, there is only one:

[root@ptqaxdb0104c ~]# vgdisplay -v VGExaDb
Using volume group(s) on command line
Finding volume group "VGExaDb"
.....
.....
--- Physical volumes ---
PV Name /dev/sda2
PV UUID 7OczLq-UUd0-ThpH-puUE-nZaI-H19Z-V55CFq
PV Status allocatable
Total PE / Free PE 71158 / 1014

Solution

With vgdisplay command there should be two physical volumes, for example:

# vgdisplay -v VGExaDb
Using volume group(s) on command line
Finding volume group "VGExaDb"
…
...
--- Physical volumes ---
PV Name /dev/sda2
PV UUID VaAFeW-hz5k-9RHy-eCjk-nr0D-UJ8X-eKew4b
PV Status allocatable
Total PE / Free PE 71158 / 24054

PV Name /dev/sda3
PV UUID AZIL8M-C122-0l8j-JTSk-wGLr-2L2y-bEXUS6
PV Status allocatable
Total PE / Free PE 142574 / 142574

The VGExaDb volume group did not get extended with the space that was freed up by the reclaimdisk step at implementation.

To reclaim the space for a physical volume, please perform step 11 in MOS note Exadata 11.2.3.2.0 release and patch (14212264) for Exadata 11.1.3.3, 11.2.1.2.x, 11.2.2.2.x, 11.2.2.3.x, 11.2.2.4.x, 11.2.3.1.x (Doc ID 1468877.1).

References

<NOTE:1468877.1> - Exadata 11.2.3.2.0 release and patch (14212264) for Exadata 11.1.3.3, 11.2.1.2.x, 11.2.2.2.x, 11.2.2.3.x, 11.2.2.4.x, 11.2.3.1.x

Attachments

This solution has no attachment