Description of problem: Prior to CFME-5.8 we use to manually extend LV 'lv_var_log' in VG 'VG-CFME', but using Option "8: Logfile configuration", when new disk is added for logfile, it creates LV 'lv-miq-logs' in *new* VG 'vg_miq_logs'. This makes space in lv_var_log unused. Why can't we just extend lv_var_log within VG-CFME just as we did before manually? Version-Release number of selected component (if applicable): 5.8.0.17-1 How reproducible: Always Steps to Reproduce: 1. Select option "8: Logfile Configuration" from `appliance_console` 2. Add new logfile volume Actual results: Expected results: Additional info: Before add additional disk for logfile (Cloudform-4.5) ~~~ [root@cfme-5 vmdb]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VG--CFME-lv_os 4.5G 2.0G 2.6G 43% / devtmpfs 4.2G 0 4.2G 0% /dev tmpfs 4.3G 4.0K 4.3G 1% /dev/shm tmpfs 4.3G 548K 4.3G 1% /run tmpfs 4.3G 0 4.3G 0% /sys/fs/cgroup /dev/vda1 509M 135M 375M 27% /boot /dev/mapper/VG--CFME-lv_home 1014M 33M 982M 4% /home /dev/mapper/VG--CFME-lv_repo 10G 33M 10G 1% /repo /dev/mapper/VG--CFME-lv_var 2.0G 1.1G 950M 54% /var /dev/mapper/VG--CFME-lv_log 10G 98M 9.9G 1% /var/www/miq/vmdb/log /dev/mapper/VG--CFME-lv_tmp 1014M 33M 982M 4% /tmp /dev/mapper/VG--CFME-lv_var_log 1014M 83M 932M 9% /var/log /dev/mapper/VG--CFME-lv_var_log_audit 509M 27M 483M 6% /var/log/audit tmpfs 862M 0 862M 0% /run/user/0 [root@cfme-5 vmdb]# pvs PV VG Fmt Attr PSize PFree /dev/vda2 VG-CFME lvm2 a-- 39.50g 0 [root@cfme-5 vmdb]# vgs VG #PV #LV #SN Attr VSize VFree VG-CFME 1 9 0 wz--n- 39.50g 0 [root@cfme-5 vmdb]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_home VG-CFME -wi-ao---- 1.00g lv_log VG-CFME -wi-ao---- 10.00g lv_os VG-CFME -wi-ao---- 4.50g lv_repo VG-CFME -wi-ao---- 10.00g lv_swap VG-CFME -wi-ao---- 9.50g lv_tmp VG-CFME -wi-ao---- 1.00g lv_var VG-CFME -wi-ao---- 2.00g lv_var_log VG-CFME -wi-ao---- 1.00g lv_var_log_audit VG-CFME -wi-ao---- 512.00m ~~~ After adding 8G of disk for logfile using option 8 from appliance_console ~~~ [root@cfme-5 log]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VG--CFME-lv_os 4.5G 2.0G 2.6G 43% / devtmpfs 4.2G 0 4.2G 0% /dev tmpfs 4.3G 4.0K 4.3G 1% /dev/shm tmpfs 4.3G 556K 4.3G 1% /run tmpfs 4.3G 0 4.3G 0% /sys/fs/cgroup /dev/vda1 509M 135M 375M 27% /boot /dev/mapper/VG--CFME-lv_home 1014M 33M 982M 4% /home /dev/mapper/VG--CFME-lv_repo 10G 33M 10G 1% /repo /dev/mapper/VG--CFME-lv_var 2.0G 1.1G 949M 54% /var /dev/mapper/vg_miq_logs-lv_miq_logs 8.0G 35M 8.0G 1% /var/www/miq/vmdb/log /dev/mapper/VG--CFME-lv_tmp 1014M 33M 982M 4% /tmp /dev/mapper/VG--CFME-lv_var_log 1014M 83M 932M 9% /var/log /dev/mapper/VG--CFME-lv_var_log_audit 509M 27M 483M 6% /var/log/audit tmpfs 862M 0 862M 0% /run/user/0 [root@cfme-5 log]# pvs PV VG Fmt Attr PSize PFree /dev/vda2 VG-CFME lvm2 a-- 39.50g 0 /dev/vdb1 vg_miq_logs lvm2 a-- 8.00g 0 [root@cfme-5 log]# vgs VG #PV #LV #SN Attr VSize VFree VG-CFME 1 9 0 wz--n- 39.50g 0 vg_miq_logs 1 1 0 wz--n- 8.00g 0 [root@cfme-5 log]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_home VG-CFME -wi-ao---- 1.00g lv_log VG-CFME -wi-ao---- 10.00g lv_os VG-CFME -wi-ao---- 4.50g lv_repo VG-CFME -wi-ao---- 10.00g lv_swap VG-CFME -wi-ao---- 9.50g lv_tmp VG-CFME -wi-ao---- 1.00g lv_var VG-CFME -wi-ao---- 2.00g lv_var_log VG-CFME -wi-ao---- 1.00g lv_var_log_audit VG-CFME -wi-ao---- 512.00m lv_miq_logs vg_miq_logs -wi-ao---- 8.00g [root@cfme-5 log]# cat /etc/fstab # /etc/fstab # Created by anaconda on Thu May 25 19:23:34 2017 # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info /dev/mapper/VG--CFME-lv_os / xfs defaults 0 0 UUID=2d9f3b6a-4b5d-4195-b3ce-04ab7be2526c /boot xfs defaults 0 0 /dev/mapper/VG--CFME-lv_home /home xfs defaults 0 0 /dev/mapper/VG--CFME-lv_repo /repo xfs defaults 0 0 /dev/mapper/VG--CFME-lv_tmp /tmp xfs defaults 0 0 /dev/mapper/VG--CFME-lv_var /var xfs defaults 0 0 /dev/mapper/VG--CFME-lv_var_log /var/log xfs defaults 0 0 /dev/mapper/VG--CFME-lv_var_log_audit /var/log/audit xfs defaults 0 0 /dev/mapper/VG--CFME-lv_log /var/www/miq/vmdb/log xfs defaults 0 0 /dev/mapper/VG--CFME-lv_swap swap swap defaults 0 0 /dev/vg_miq_logs/lv_miq_logs /var/www/miq/vmdb/log xfs rw,noatime 0 0 ~~~
Also notice that the /etc/fstab also contains two entries for /var/www/miq/vmdb/log /dev/mapper/VG--CFME-lv_log /var/www/miq/vmdb/log xfs defaults 0 0 /dev/vg_miq_logs/lv_miq_logs /var/www/miq/vmdb/log xfs rw,noatime 0 0 This makes console complaint and also produces unpredictable results because of the duplicate entry.
When the Logfile Configuration was added to the appliance_console it was decided to leave the initial log volume untouched by design. It was by design to ensure any logs that had been written to that initial volume before the the logfile configuration was changed would not be lost. I am going to close this BZ as NOTABUG. If it is felt that this is not the correct thing to do please reopen with more details. Thank you. JoeV