--scan
--extend <volume> [ <n>m | <n>g | <n>t --remaining ]
--extend --all
--reset
[admin@server4889csa ~]$
Verbose help: sys volmgt --hhelp
The verbose help information for the scripts provides more information about what the tool is used
for.
[admin@server4889csa ~]$ sys volmgt --hhelp
This script provides for the ability to extend the sizes of volumes on this
system. In order for a volume to be extended in size, the disk that hosts
the volume must first be increased in size using the tools that are used
to manage deployed virtual machines (VMware).
The following example illustrates how to add 20 GiB of storage to the
application log volume (/var/log/Avaya). This volume is located on the second
disk of the system and so this example assumes that disk 2 has been increased
in size by 20 GiB.
sys volmgt --extend /var/log/Avaya 20g
The above example will do two things:
1) It will extend the size of the LVM logical volume by 20 GiB.
2) It will then extend the size of the Linux file system that is
located inside that volume to the new size of the LVM logical
volume.
Step (2) above may take several minutes to complete for larger volumes. If,
for some reason, this second operation is interrupted, it can be re-run
using the same command, but WITHOUT specifying the size argument. For example,
the following command is used to perform step (2) only for the application
log volume (/var/log/Avaya).
sys volmgt --extend /var/log/Avaya
If in doubt as to whether or not all file systems have been fully extended in
their respective volumes, step (2) can be executed across all volumes using
a single command as follows:
sys volmgt --extend --all
Performing step (2) on a file system that is already fully extended in its
LVM volume is a null operation (does no harm).
Note the following general points regarding this script:
- The extending of a volume cannot be undone. Make sure the correct volume
is being extended, and by the correct size. To confirm any extend
operation, the user is required to enter the response "confirm"
(case insensitive).
- In order to avoid impacting system performance, avoid performing extend
operations during periods of high traffic.
- Extend operations are performed by a background process, in order to
avoid interference due to loss of an SSH connection. Avoid powering down
or rebooting a server while there is a background operation in progress.
The presence of a running background operation can be queried as follows:
System layer commands
October 2018
Deploying the Avaya Aura
®
Web Gateway
31