Symptoms -
- Customers may come up with the concern that the /storage/dblog shows as a usage rate of 65% and above occasionally. This may not be showing any impact on the environment.
- Below is the scenario -
root@vc_name [ ~ ]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs 7.9G 740K 7.9G 1% /dev/shm
tmpfs 7.9G 684K 7.9G 1% /run
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sda3 11G 5.9G 4.3G 59% /
tmpfs 7.9G 1.6M 7.9G 1% /tmp
/dev/mapper/netdump_vg-netdump 985M 1.3M 916M 1% /storage/netdump
/dev/mapper/db_vg-db 9.8G 364M 8.9G 4% /storage/db
/dev/mapper/dblog_vg-dblog 15G 9.4G 4.6G 68% /storage/dblog
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 23M 9.2G 1% /storage/imagebuilder
/dev/mapper/log_vg-log 9.8G 2.9G 6.4G 31% /storage/log
/dev/mapper/autodeploy_vg-autodeploy 9.8G 23M 9.2G 1% /storage/autodeploy
/dev/mapper/archive_vg-archive 50G 14G 34G 29% /storage/archive
/dev/sda1 120M 34M 77M 31% /boot
/dev/mapper/updatemgr_vg-updatemgr 99G 79M 94G 1% /storage/updatemgr
/dev/mapper/seat_vg-seat 25G 1.4G 22G 6% /storage/seat
/dev/mapper/core_vg-core 50G 2.3G 45G 5% /storage/core
du -a /storage/dblog/ | sort -n -r | head -n 20
total 16G
drwx------ 2 vpostgres vpgmongrp 4.0K May 3 2023 [0m [01;34marchive_status [0m
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:40 00000001000002BF000000ED
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:40 00000001000002BF000000EA
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:40 00000001000002BF000000EE
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:40 00000001000002BF000000F0
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:44 00000001000002BF000000E9
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:50 00000001000002BF000000EC
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:55 00000001000002BF000000EB
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:55 00000001000002BF000000EF
-rw------- 1 vpostgres vpgmongrp 16M Mar 18 19:57 00000001000002BF000000F4
root@vc_name[ ~ ]# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "select name, setting, unit from pg_settings where name in ('min_wal_size', 'max_wal_size')"
name | setting | unit
--------------+---------+------
max_wal_size | 655 | 16MB
min_wal_size | 655 | 16MB
(2 rows)
- From above parameter, 16M*655= 10480 MB = 10.5GB < 15G
root@vc_name [ ~ ]# /opt/vmware/vpostgres/current/bin/psql -U postgres -c "select pg_postmaster_start_time()"
pg_postmaster_start_time
-------------------------------
yyyy-mm-dd22:12:07.604504+00
(1 row)