-
Bitrix Virtual Appliance v7.x
-
What's New
-
Installation of Bitrix Environment (BitrixEnv) for Linux
-
Launching Bitrix Virtual Appliance
-
VMBitrix.CRM
-
Installation and Migration of Bitrix24 Products to BitrixVA/BitrixEnv
-
1. Manage servers in the pool
-
2. Manage localhost
-
3. Configure MySQL servers
-
4. Configure Memcached Servers
-
5. Background Tasks in the pool
-
6. Configure pool sites
-
1. Create Site
-
2. Delete Site
-
3. Change Cron Tasks on Site
-
4. Change E-mail Settings on Site
-
5. Change HTTPS Settings on Site
-
6. Change Backup Settings on Site
-
7. Configure NTLM Authorization for all Sites
-
8. Configure Optional Services (xmppd|smtpd) for Site
-
9. Bitrix Composite Site
-
10. Configure Site Options
-
11. Show Sites with Errors
-
-
7. Manage Sphinx in the pool
-
8. Manage Web Nodes in the pool
-
9. Monitoring in the pool
-
10. Configure Push/RTC Service
-
Additional Settings for BitrixAV/BitrixEnv
-
Modification of BitrixVA Standard Settings without Disabling Autotuning
-
Adding SSL-certificates in BitrixVA/BitrixEnv
-
Expanding BitrixVA Disk Space
-
Connecting Swap Partition
-
Manual Configuration of Memcached
-
Correct Mounting of Windows-Resources
-
Execution of All Agents via Cron
-
Mounting Options
-
Connecting IDE
-
Packet Source Codes (starting from version 7.3.0!)
-
Beta version of BitrixEnv/VMBitrix.CRM
-
PHP-Extensions Manual Enabling
-
BitrixVA proxying settings
-
-
BitrixVA API for Providers
-
How to create BitrixVM image for cloning
-
-
Bitrix Virtual Appliance Contents
-
Introduction
-
Service configuration
-
BitrixVM Configuration
-
-
Archive
-
Bitrix Virtual Appliance v4.3 (Archived)
-
Introduction
-
Running the Bitrix Virtual Appliance
-
Configuring the SMTP Mail Server
-
Creation of a Master-Slave Cluster
-
Adding a Site
-
Automatic Backups
-
Sphinx Search Engine Setup
-
Update of Bitrix Virtual Appliance
-
Restoring a Web Project from a backup copy
-
Additional BitrixVA settings
-
-
Bitrix Virtual Appliance v5.x (Archived)
-
Installation of Bitrix Environment for Linux 5.x
-
Installation of the VA VMware Edition
-
Migration of the Bitrix product to a VA
-
Host management
-
Configure MySQL servers
-
Manage local server
-
Configure the memcached servers
-
Background tasks in the pool
-
Manage the sites in the pool
-
Sphinx Search Engine Setup
-
Manage web-servers
-
Monitoring in pool
-
Additional BitrixVA settings
-
-
Increasing Size of BitrixVA LVM-Partition
Lesson 79 out of 182
Attention! For operations, described in this lesson, *nix-systems administration knowledge is required. Prior to starting of operations, it is recommended to perform a full «Bitrix Virtual Appliance» backup.
Attention! Logic Volume Manager LVM2 is installed by default in CentOS 7 during the automatic partitioning of the disk during the system installation phase (in case if BitrixEnv is installed via bitrix_env.sh script on the CentOS 7). In such case, the size change for LVM-partition will differ from previous methods.
Scenario: the size of system disk was increased from 20GB to 100GB, as was done previously in VMWare Player.
Then, the actions to change LVM-partition size will be the following:
- Check, what devices/partitions are available at the moment via the command:
fdisk -l
- Verify, that the space did not increase automatically via the command:
df -h
Volume group name and the name volume are also visible (we will have different ones):
- cl - volume group name;
- root - volume name.
- Create a new sda3 partition - partition type: Linux LVM (code type 8e) on the unpartitioned space. To do that, start working with the sda device via the command:
fdisk /dev/sda
- Next, create a new partition via the n command:
- primary (primary partition) - p and
Partition number (1-3, default 3): 3
command (because we had 2 logical partitions sda1 and sda2 - p.1); - in this case, first and last sectors are selected by default - this way, partition will be created by using all available free space on disk;
- indicate partition type - t and
Partition number (1-3, default 3): 3
command; - enter partition code type, corresponding Linux LVM -
8e
; - see the partition table - enter p command and make sure, that all is correct;
- Partition sda3 is created. To save the updated partition table and to exit from fdisk - w command.
- primary (primary partition) - p and
- For the system to load the new partition table, reload the Virtual Appliance:
reboot
- After the reset, it is necessary to create a sda3 physical volume:
pvcreate /dev/sda3
- Next, expand the volume group to a new space, using the cl volume group name (which we have memorized previously in p.2):
vgextend /dev/cl /dev/sda3
- Now, expand the logical volume, by using the root volume name (hich we have memorized previously in p.2):
lvextend -l+100%FREE /dev/cl/root
- Scan disks for the for the availability of volume groups and activate all volume groups that are found:
vgscan vgchange -ay
- Find the type of file system:
file -s /dev/sda1
See, that file system is XFS.
- And finally, expand XFS file system (may require time):
xfs_growfs /dev/cl/root
Note: If the file system is not XFS, but, for example, id ext4 or reiserfs, then the commands will be the following (with account of cl - to group name and root - volume name from p.2):resize2fs /dev/cl/root
- for ext4;resize_reiserfs /dev/cl/root
- for reiserfs;
- Check the final result:
df -h