The only thing I didnt like about the deployment is that just about ALL of the storage is presented to ASM as part of the install, leaving little for the OS on each node. While I know you can expand your storage capabilities using NFS and other solutions, I focused on expanding the /cloudfs mount point that was setup as part of our ODA deployment and is visible to both nodes.
The default size of this volume is 50G, and it turns out it was pretty simple to resize to 200G at the cost of stealing a bit of space from our +RECO asm diskgroup.
[grid@uoda2 ~]$ . oraenv
ORACLE_SID = [+ASM1] ? +ASM2
The Oracle base has been set to /u01/app/grid
[grid@uoda2 ~]$ /sbin/acfsutil size +161061273600 /cloudfs
acfsutil size: new file system size: 214748364800 (204800MB)
[grid@uoda2 ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolRoot
30G 3.1G 25G 12% /
/dev/md0 487M 36M 426M 8% /boot
/dev/mapper/VolGroupSys-LogVolOpt
59G 8.7G 47G 16% /opt
/dev/mapper/VolGroupSys-LogVolU01
97G 38G 55G 41% /u01
tmpfs 127G 223M 126G 1% /dev/shm
/dev/asm/acfsvol-154 200G 33G 168G 17% /cloudfs
Here's how I found out it was using space from the RECO group:
[grid@uoda2 ~]$ asmcmd
ASMCMD> volinfo -a
Diskgroup Name: RECO
Volume Name: ACFSVOL
Volume Device: /dev/asm/acfsvol-154
State: ENABLED
Size (MB): 204800
Resize Unit (MB): 32
Redundancy: HIGH
Stripe Columns: 4
Stripe Width (K): 128
Usage: ACFS
Mountpath: /cloudfs
No comments:
Post a Comment