Azure CloudGuard - Increase the disk size of an already deployed instance

[Simon_Macpherso]

Hello,

We are performing an R18.10 IPU upgrade on 2x Azure HA clusters from version R80.30 jhf 246.

As part of this upgrade, we need to add additional space to the disks allocated to the VMs as there is insufficient free space for snapshots (increasing disk size from 100GB to 200GB)

Per sk156552, I’ve increased the size of the disk on the standby device. However, after the device comes back online, I can see the additional storage has been added (per the size of disk dev/sda) but there is no new partition added.

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...

Before the VM was stopped, I didn’t run rm /etc/autogrow. Not sure what impact this would have had if any.

Output of parted -l and blkid on standby member

[Expert@cg2:0]# parted -l

Model: Msft Virtual Disk (scsi)

Disk /dev/sda: 215GB

Sector size (logical/physical): 512B/4096B

Partition Table: gpt

Disk Flags:

Number Start  End   Size  File system Name Flags

 1   1049kB 316MB  315MB  ext3        boot

 2   316MB  8902MB 8586MB

 3   8902MB 107GB  98.5GB           lvm

Model: Msft Virtual Disk (scsi)

Disk /dev/sdb: 215GB

Sector size (logical/physical): 512B/4096B

Partition Table: msdos

Disk Flags:

Number Start  End  Size  Type   File system Flags

 1   1049kB 215GB 215GB primary ntfs

Model: Linux device-mapper (linear) (dm)

Disk /dev/mapper/vg_splat-lv_current: 21.5GB

Sector size (logical/physical): 512B/4096B

Partition Table: loop

Disk Flags:

Number Start End   Size  File system Flags

 1   0.00B 21.5GB 21.5GB xfs

Model: Linux device-mapper (linear) (dm)

Disk /dev/mapper/vg_splat-lv_log: 46.2GB

Sector size (logical/physical): 512B/4096B

Partition Table: loop

Disk Flags:

Number Start End   Size  File system Flags

 1   0.00B 46.2GB 46.2GB xfs

 [Expert@cg2:0]# blkid

/dev/root: UUID="8cc4b0a4-2765-466c-84be-562a7e80dcb2" TYPE="xfs"

/dev/sdb1: LABEL="Temporary Storage" UUID="30783B2A783AEE6A" TYPE="ntfs"

/dev/sda1: LABEL="/boot" UUID="00c51a5a-ed89-4b42-8b9f-e6f0d4a87569" TYPE="ext3" PARTUUID="a18a8c6d-6ea1-40fe-b8b5-72fd41ef1e9d"

/dev/sda2: PARTUUID="acdf6f85-1ce5-4759-9a16-54fdf50c73b5"

/dev/sda3: UUID="ulz7TA-2ERl-kDMV-916S-ZOoM-6FeI-gPU1r5" TYPE="LVM2_member" PARTUUID="063ee620-87ff-464b-a88f-86c4da4e3b8c"

/dev/mapper/vg_splat-lv_log: UUID="b216623f-a8f1-4503-a706-2eb94bf3476e" TYPE="xfs"

[Simon_Macpherso]

For anyone interested, this can be resolved by rerunning autogrow.sh script in /bin. After the gateway reboots, create a physical volume i.e. pvcreate /dev/sda4, then add the newly defined physical volume to the existing 'vg_splat' partition (this is the Volume Group that manages disk space for Gaia), i.e. vgextend vg_splat /dev/sda4. Open lvm_manager, the additional disk space will be available as free space.