How We Are Adding new disk to ACFS disk group or extending/increasing the size of ACFS file system diskgroup
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a multi-platform, scalable file system, and storage management technology that extends Oracle Automatic Storage Management (Oracle ASM) functionality to support all customer files. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) provides volume management services and a standard disk device driver interface to clients.
In this scenario We assume that disks have been formated by udev utulity.
So here We go
1. Check current status of disks)
[grid@node1 ~]$ df -h
/dev/asm/archivelog-1 100G 20G 81G 20% /archivelog
/dev/asm/redo2-1 10G 8.6G 1.5G 86% /redo2
/dev/asm/oradat-1 180G 179G 1G 99% /oradata
/dev/asm/redo1-147 10G 8.6G 1.5G 86% /redo1
2. List ASM disks
[grid@node1 ~]$ asmcmd -p
ASMCMD [+] > lsdg
State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED EXTERN N 512 4096 4194304 819200 30356 0 30356 0 Y DATA/
3. Check ACFS disks info
ASMCMD> volinfo –all
5. If you have free size in ASM than resize related path (In my case I have 30G free disk size)
[grid@node1 ~]$ acfsutil size 220G /oradata -> size from 180Gb to 220Gb
acfsutil size: Resizing file system in steps
acfsutil size: Resizing file system to 0.2109 TB
acfsutil size: Resizing file system to 0.2148 TB
acfsutil size: new file system size: 236223201280 (225280MB)
6. If We need to add new disk to ASM than follow below steps:
A- Check both nodes for new disk is exist or not. Do not forget to check permissions:
[root@node1 ~]#fdisk -l
Disk /dev/sdd: 549.8 GB, 549755813888 bytes, 1073741824 sectors
Units = sectors of 1 * 512 = 512 bytes
[root@node2 ~]#fdisk -l
Disk /dev/sdd: 549.8 GB, 549755813888 bytes, 1073741824 sectors
Units = sectors of 1 * 512 = 512 bytes
B- Check Disk IDs by following command
[root@node1 ~]# /usr/lib/udev/scsi_id -g -u /dev/sdd —-> sdd is our new disk
46000c29eb5d0f26a5aaf
[root@node2 ~]# /usr/lib/udev/scsi_id -g -u /dev/sdd —-> sdd is our new disk
46000c29eb5d0f26a5aaf
C- Edit “/etc/udev/rules.d/99-asm.rules” files on both nodes
Node1:
root@node1 ~]# vi /etc/udev/rules.d/99-asm.rules
KERNEL==”sd“, PROGRAM==”scsi_id –page=0x83 –whitelisted –device=/dev/%k”, RESULT==”66000c29962435913c”, SYMLINK+=”DATA/disks/oraasmdisk”, OWNER =”grid”, GROUP=”dba”, MODE=”0660″ KERNEL==”sd“, PROGRAM==”scsi_id –page=0x83 –whitelisted –device=/dev/%k”, RESULT==”46000c29eb5d0f26a5″, SYMLINK+=”DATA/disks/oraasmdisk2″, OWNER=”grid”, GROUP=”dba”, MODE=”0660″ ——-> New disk info here
Node2:
root@node2 ~]# vi /etc/udev/rules.d/99-asm.rules
KERNEL==”sd“, PROGRAM==”scsi_id –page=0x83 –whitelisted –device=/dev/%k”, RESULT==”66000c29962435913c”, SYMLINK+=”DATA/disks/oraasmdisk”, OWNER =”grid”, GROUP=”dba”, MODE=”0660″ KERNEL==”sd“, PROGRAM==”scsi_id –page=0x83 –whitelisted –device=/dev/%k”, RESULT==”46000c29eb5d0f26a5″, SYMLINK+=”DATA/disks/oraasmdisk2″, OWNER=”grid”, GROUP=”dba”, MODE=”0660″ ——-> New disk info here
D- Run below command on both nodes
Node1:
[root@node1 ~]# udevadm control –reload-rules && udevadm trigger
Node2:
[root@node2 ~]# udevadm control –reload-rules && udevadm trigger
E- Check disks info on both nodes
Node 1 and Node 2
[grid@node1 ~]$ asmcmd lsdsk
Path
/dev/DATA/disks/oraasmdisk
/dev/DATA/disks/oraasmdisk2
[root@node1 ~]# ls /dev/DATA/disks/
oraasmdisk oraasmdisk2
[root@node1 ~]# ls -laL /dev/DATA/disks/
brw-rw—- 1 grid dba 8, 48 Sep 1 18:56 oraasmdisk2
[root@node1 ~]# ls -l /dev/DATA/disks/
lrwxrwxrwx 1 root root 9 Sep 1 18:56 oraasmdisk2 -> ../../sdd
F- Add new disk to ASM instance:
[grid@node1 ~]$ sqlplus “/as sysasm”
SQL> alter diskgroup DATA add disk ‘/dev/DATA/disks/oraasmdisk2’ rebalance power 6;
SQL> select name,STATE,header_status ,path from v$asm_disk;
NAME STATE HEADER_STATUS PATH
——— ——– ———— ————————————————————————–
DATA_0000 NORMAL MEMBER /dev/DATA/disks/oraasmdisk
DATA_0001 NORMAL MEMBER /dev/DATA/disks/oraasmdisk2 -> Our disk