Partitioning problem and recommended scheme

[rustynail]

Hi expert,
We are using Vicibox 7 install on physical server with Xeon 4 core cpu, 4GB ram and 250GB hard in raid. I am new to vicidial and a little experienced with linux partitioning. On my new job I saw this strange partitioning scheme being used by the datacenter guys who provide servers.

vicibox7:~ # df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 123M 3.8G 4% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/system-root 20G 16G 3.0G 85% /
/dev/mapper/system-root 20G 16G 3.0G 85% /var/tmp
/dev/mapper/system-root 20G 16G 3.0G 85% /var/opt
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/pgsql
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/mailman
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/libvirt/images
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/mariadb
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/mysql
/dev/mapper/system-root 20G 16G 3.0G 85% /tmp
/dev/mapper/system-root 20G 16G 3.0G 85% /usr/local
/dev/mapper/system-root 20G 16G 3.0G 85% /var/spool
tmpfs 6.0G 0 6.0G 0% /var/spool/asterisk/monitor
/dev/mapper/system-root 20G 16G 3.0G 85% /var/crash
/dev/mapper/system-root 20G 16G 3.0G 85% /srv
/dev/mapper/system-root 20G 16G 3.0G 85% /opt
/dev/mapper/system-root 20G 16G 3.0G 85% /boot/grub2/i386-pc
/dev/mapper/system-root 20G 16G 3.0G 85% /var/log
/dev/mapper/system-root 20G 16G 3.0G 85% /boot/grub2/x86_64-efi
/dev/mapper/system-root 20G 16G 3.0G 85% /var/lib/named
/dev/mapper/system-root 20G 16G 3.0G 85% /home
vicibox7:~ #
vicibox7:~ # fdisk -l

Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e1bbc

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 500113407 500111360 238.5G 8e Linux LVM

Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e1bbc

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 500113407 500111360 238.5G 8e Linux LVM

Disk /dev/md126: 238.5 GiB, 256058064896 bytes, 500113408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e1bbc

Device Boot Start End Sectors Size Id Type
/dev/md126p1 * 2048 500113407 500111360 238.5G 8e Linux LVM

Disk /dev/mapper/system-root: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/system-swap: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

vicibox7:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
└─md126 9:126 0 238.5G 0 raid1
└─md126p1 259:0 0 238.5G 0 md
├─system-root 254:0 0 20G 0 lvm /
└─system-swap 254:1 0 2G 0 lvm [SWAP]
sdb 8:16 0 238.5G 0 disk
└─md126 9:126 0 238.5G 0 raid1
└─md126p1 259:0 0 238.5G 0 md
├─system-root 254:0 0 20G 0 lvm /
└─system-swap 254:1 0 2G 0 lvm [SWAP]
vicibox7:~ #

Now the problem is, as you migh have guessed, under load space becomes an issue and quickly fills up to 95% as recordings grow and I have to use FTP script to move MP3 files to our ftp and remove wave files from ORIG.
I want to know what are my options to correct this issue as server is now in production and has almost 100 - 150 calls during the office timings. Can I remove un-needed partitions like /var/temp and allocate their space to root? Also I see /temp is also mounted with 20GB so can I resize it to free some space from it and add to root / ?

I also planned to attach a 100GB or 250GB hard drive and mount it for moving files from ORIG folder on daily basis using cron.

Also I see mysql-bin.xxxx files being generated for replication so what is best option to backup those files? Should I move them to ftp also? any impact of simply copying to ftp and then deleting them or should I use mysql purge method?

Need your help urgently as its horrible to free space on daily basis even sundays

Thanks,
Jedi

[rustynail]

No expert here to help?

[Kumba]

You need to reinstall and setup the partitioning so that 4 gigabytes of hard drive is used for the swap partition and the rest of the entire hard drive is used for / (root). There is no way to make a 20-gigabyte hard drive partition work for anything other then a dev environment.

[rustynail]

Sorry for being late as these days and nights were like hell.... setting up many clients and managing their stuff..

Thank you for your reply dear Kumba, yes that partitioning was created by datacenter guys and I have instructed them to change. But you didn't mentioned the need for tmpfs partition for monitor recordings for fast mixing? Like this...

tmpfs 6.0G 448K 6.0G 1% /var/spool/asterisk/monitor

Or I can go fine without creating this separate partition?

Thanks again.. Cheers!

[williamconley]

Sorry for being late as these days and nights were like hell.... setting up many clients and managing their stuff..

Thank you for your reply dear Kumba, yes that partitioning was created by datacenter guys and I have instructed them to change. But you didn't mentioned the need for tmpfs partition for monitor recordings for fast mixing? Like this...

tmpfs 6.0G 448K 6.0G 1% /var/spool/asterisk/monitor

Or I can go fine without creating this separate partition?

Thanks again.. Cheers!

The stock system built by Kumba will create this entry in fstab:

Code: Select all

tmpfs   /var/spool/asterisk/monitor       tmpfs      rw,size=6G              0 0


This is not directly related the hard drive partitioning as it will use memory and swap.