Created on
11-15-2017
07:41 AM
Edited on
04-04-2024
08:53 AM
By
chall_FTNT
Description
Solution
Method 1 - Add new virtual disks and extend the logical volume.
Note:
Since the SQL database operations may consume a lot of disk time, it is recommended to locate the FortiAnalyzer disks on a datastore (physical drive or array) that is not shared with other disk-consuming VMs, in order to avoid performance issues.
Specify the Advanced Options if needed, or select 'Next' and 'Finish' in the next two dialog boxes.
exec lvm extend
This operation will need to reboot the system.
Do you want to continue? (y/n)y
Note:
Although the above prompt only mentions a reboot, FortiAnalyzer will first perform a file system check (FSCK). If no errors occur, it will proceed to resize the file system (RESIZE2FS). With large file systems, the file system check may take significantly longer than a simple reboot.
The output below (only visible via the ESXi virtual console) shows the two steps:
The system is going down NOW !!
Rescan disks...
add new disk2: 200GB
Extend /dev/mdvg/mdlv...
Fsck /dev/mdvg/mdlv...
Done, no error.
Resize2fs /dev/mdvg/mdlv...
Please stand by while rebooting the system.
[ 3698.432925]reboot: Restarting system
Before FortiAnalyzer/FortiManager 5.6.6 and 6.0.3, increasing the size of an already used virtual disk required format in order to utilize the additional space.
As of FortiAnalyzer/FortiManager 5.6.6 and 6.0.3:
The examples below are from VMware ESXi (vSphere) 6.7.0, but the process is similar for most hypervisor types.
exec lvm info
LVM Status: OK
LVM Size: 150GB
File System: ext4 147GB
Disk1 : Used 150GB of 160GB
Disk2 : Unavailable 0GB
Disk3 : Unavailable 0GB
Disk4 : Unavailable 0GB
Disk5 : Unavailable 0GB
Disk6 : Unavailable 0GB
Disk7 : Unavailable 0GB
Disk8 : Unavailable 0GB
exec lvm extend
This operation will need to reboot the system.
Do you want to continue? (y/n)y
Note:
Although the above prompt only mentions a reboot, FortiAnalyzer will first perform a file system check (FSCK) and, if no errors, will proceed to resize the file system (RESIZE2FS). With large file systems, the file system check may take significantly longer than a simple reboot.
The output below (only visible via the ESXi virtual console) shows the two steps:
The system is going down NOW !!
Rescan disks...
extend disk1: 160GB
Extend /dev/mdvg/mdlv...
Fsck /dev/mdvg/mdlv...
Done, no error.
Resize2fs /dev/mdvg/mdlv...
Please stand by while rebooting the system.
[5951271.416233] reboot: Restarting system
exec lvm info
LVM Status: OK
LVM Size: 160GB
File System: ext4 156GB
Disk1 : Used 160GB
Disk2 : Unavailable 0GB
Disk3 : Unavailable 0GB
Disk4 : Unavailable 0GB
Disk5 : Unavailable 0GB
Disk6 : Unavailable 0GB
Disk7 : Unavailable 0GB
Disk8 : Unavailable 0GB
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.