disk resize ASM

[Roshan]

Oracle Database 12.2.0

RHEL 7.4

 

Hello Team,

 

Recently the all ASM disks on a server were extended from 250 GB to 500 GB each. But I see from the query below that the total size is still 1 TB
pastedImage_0.png
 

I did 'ALTER DISK GROUP DATA RESIZE ALL' but total size is still 1 TB

 

SQL> SELECT

  2    name                                GROUP_NAME

  3  , round ( total_mb)                   TOTAL_MB

  4  , round ( (total_mb - free_mb) )      USED_MB

  5  , round ( free_mb)                    FREE_MB

  6  , ROUND((1- (free_mb / total_mb))*100,2  )  USED

  7  , (100 - ROUND((1- (free_mb / total_mb))*100,2))  FREE

  8  FROM

  9    v$asm_diskgroup

10  ORDER BY

11    name

12  /

 

 

GROUP_NAME                       TOTAL_MB    USED_MB    FREE_MB       USED       FREE

------------------------------ ---------- ---------- ---------- ---------- ----------

DATA                              1023968    1018400       5568      99.46        .54

                               ---------- ----------

Grand Total:                      1023968    1018400

 

[grid@RH-DATWHSE-DEV ~]$ sh chasmmapping.sh

ASM disk DISK1 based on /dev/sdc1 [8, 33]

ASM disk DISK2 based on /dev/sdd1 [8, 49]

ASM disk DISK3 based on /dev/sde1 [8, 65]

ASM disk DISK4 based on /dev/sdi1 [8, 129]

 

fdisk results:

Disk /dev/sdd: 536.9 GB, 536870912000 bytes, 1048576000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk label type: dos

Disk identifier: 0x36ac345b

 

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdd1            2048   524287999   262142976   83  Linux

 

Disk /dev/sdc: 536.9 GB, 536870912000 bytes, 1048576000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk label type: dos

Disk identifier: 0x4e6e1670

 

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdc1            2048   524287999   262142976   83  Linux

 

Disk /dev/sde: 536.9 GB, 536870912000 bytes, 1048576000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk label type: dos

Disk identifier: 0x4042930c

 

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sde1            2048   524287999   262142976   83  Linux

 

Disk /dev/sdi: 536.9 GB, 536870912000 bytes, 1048576000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk label type: dos

Disk identifier: 0xad2667fc

 

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdi1            2048   524287999   262142976   83  Linux

 

Please advise if I delete the partition tables for example /dev/sdi1 and create new

Regards,

Roshan

[Roshan]

According to the doc below data won't be lost

https://jarneil.wordpress.com/2008/04/22/expanding-an-asm-disk/

[ErmanArslansOracleBlog]

Yes.
If your partitions which are used by ASM are not resized, then you need to recreate them. Recreate them with the new size..
You do it with fdisk. Enlarging a partiton doesnt delete data.. But be careful. Follow the documents carefully if u didnt do this kind of a work earlier..

[Roshan]

Hi Erman,

the operation was successful. I have added new disks of 500 GB but I cannot label them

./asmcmd afd_unlabel /dev/sdf1
./asmcmd afd_label DISK5 /dev/sdf1 --init

[grid@RH-DATWHSE-DEV bin]$ ./asmcmd afd_label DISK5 /dev/sdf1 --init
No devices to be labeled.

[grid@RH-DATWHSE-DEV bin]$ asmcmd afd_unlabel /dev/sdf1
ASMCMD-9520: AFD is not 'Loaded'

[ErmanArslansOracleBlog]

Why do you label them?

In an ASM resize operation, you need to do the following only;

1) Backup the database(s) contained inside the associated diskgroup.

2) Shutdown the databases contained inside the associated diskgroup.

3) Dismount the associated diskgroup to verify no client database connections are accessing this specific diskgroup

4)Resize your physical disk/LUN at OS/hardware level.

5)Mount back the diskgroup

6)Resize the ASM disk with ALTER DISKGROUP RESIZE DISK command.

[ErmanArslansOracleBlog]

If you are adding a new disk or something;
please create another issue for it, and please provide all of the details.. (about your environment, version, and recent changes(like upgrade..))

[Roshan]

Ok thanks.

I will create a separate request.