- Go to the Hypervisor and increase the size of the /opt disk.
- SSH into the FortiSIEM node as the root user.
- Run lsblk to learn the disk and its partition mounted on /opt.
For example:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
...
sdb 8:16 0 100G 0 disk
├─sdb1 8:17 0 22.4G 0 part [SWAP]
└─sdb2 8:18 0 68.9G 0 part /opt
...
- Install the utilities to extend the disk.
yum -y install cloud-utils-growpart gdisk
- Run growpart to extend the partition size of the disk:
growpart <disk> <parition number>
For example:
growpart /dev/sdb 2
CHANGED: partition=2 start=50782208 old: size=144529408 end=195311616 new: size=473505759 end=524287967
- Verify the extended size using the 'lsblk' command.
- Run xfs_growfs to extend the filesystem of the disk partition.
xfs_growfs <disk partition>
For example:
xfs_growfs /dev/sdb2
meta-data=/dev/sdb2 isize=512 agcount=4, agsize=4516544 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=18066176, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=8821, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
data blocks changed from 18066176 to 59188219
- Run 'df -h' and note the new size of /opt.
Filesystem Size Used Avail Use% Mounted on
...
/dev/sdb2 226G 6.1G 220G 3% /opt
Note:
Although this process is valid to increase /opt size, in FortiSIEM's normal operation, a full /opt disk could be a potential issue. If /opt disk continues growing, it should be appropriate to check through a Support ticket.
Related article:
Troubleshooting Tip: High root disk usage on collector due to clickhouse service
|
