# dbengine directory growing despite configured disk usage limits **URL:** \ **Category:** Help\ **Created:** [January 3, 2023, 10:24am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703 "2023-01-03T10:24:02Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [January 3, 2023, 10:24am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/1 "2023-01-03T10:24:02Z")
## Problem/Question I have a similar issue to [this](https://community.netdata.cloud/t/dbengine-not-respecting-configured-disk-usage-limits/3516). Our netdata instances seem to not respect settings from netdata.conf. We run netdata v1.36.1 on tens of CentOS Linux release 7.9.2009 (Core) nodes. [root@host netdata]# du -h | sort -hr | head 1.5G . 1.2G ./netdata 886M ./netdata/dbengine After a restart of the service, disk usage drops but climbs back up later. [root@host netdata]# du -h 248M ./dbengine 502M . ![Screenshot from 2023-01-03 11-00-01](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/a/af10dbd97c25721f5416d3bd1f8e7a915bc9bdf4.png) The netdata-meta.db file stays under 250M, while the dbengine directory grows to fill the /var partition. Our /etc/netdata/netdata.conf: ```auto [global] ... dbengine disk space = 256 [db] dbengine multihost disk space MB = 256 [root@host netdata]# curl -s localhost:19999/netdata.conf ... [global] run as user = netdata process scheduling policy = idle OOM score = 1000 # glibc malloc arena max for plugins = 1 # glibc malloc arena max for netdata = 1 # libuv worker threads = 16 # hostname = host # host access prefix = # enable metric correlations = yes # metric correlations method = ks2 # timezone = Europe/Amsterdam # pthread stack size = 8388608 [db] dbengine disk space MB = 256 # option 'retention' is not used. retention = 3600 dbengine multihost disk space MB = 256 # update every = 1 # mode = dbengine # dbengine page cache with malloc = no # dbengine page cache size MB = 32 # memory deduplication (ksm) = yes # cleanup obsolete charts after secs = 3600 # gap when lost iterations above = 1 # storage tiers = 1 # dbengine page fetch timeout secs = 3 # dbengine page fetch retries = 3 # dbengine page descriptors in file mapped memory = no # cleanup orphan hosts after secs = 3600 # delete obsolete charts files = yes # delete orphan hosts files = yes # dbengine pages per extent = 64 # enable zero metrics = no ... ``` Looking in /var/log/netdata/error.log, housekeeping is being done: ```auto 2023-01-03 10:03:15: netdata INFO : MAIN : Deleting data file "/var/cache/netdata/dbengine/datafile-1-0000000501.ndf". 2023-01-03 10:03:15: netdata INFO : MAIN : Deleting data and journal file pair. 2023-01-03 10:03:15: netdata INFO : MAIN : Deleted journal file "/var/cache/netdata/dbengine/journalfile-1-0000000501.njf". 2023-01-03 10:03:15: netdata INFO : MAIN : Deleted data file "/var/cache/netdata/dbengine/datafile-1-0000000501.ndf". 2023-01-03 10:03:15: netdata INFO : MAIN : Reclaimed 14479360 bytes of disk space. ``` The pattern seems to be that after a restart of the netdata service, the size of the dbengine directory remains the same for about a day, and then keeps growing. I found no cron jobs that interfere with netdata housekeeping. Are we setting the limit settings in netdata.conf correctly? ## Relevant docs you followed/actions you took to solve the issue Tried following combinations of settings with same result, based on - [https://github.com/netdata/netdata/blob/master/daemon/config/README.md#db-section-options](https://github.com/netdata/netdata/blob/master/daemon/config/README.md#db-section-options) - [Database Configuration Reference | Learn Netdata](https://learn.netdata.cloud/docs/store/change-metrics-storage) - [https://github.com/netdata/netdata/blob/master/daemon/config/README.md#db-section-options](https://github.com/netdata/netdata/blob/master/daemon/config/README.md#db-section-options) ```auto 1: [global] dbengine disk space = 256 [db] empty 2: [global] empty [db] dbengine multihost disk space MB = 256 3: [global] dbengine disk space = 256 [db] dbengine multihost disk space MB = 256 ``` ## Environment/Browser/Agent’s version etc ```auto [root@host netdata]# netdata -V netdata v1.36.1 [root@host netdata]# which netdatacli /sbin/netdatacli [root@host netdata]# netdatacli aclk-state ACLK Available: Yes ACLK Version: 2 Protocols Supported: Protobuf Protocol Used: Protobuf MQTT Version: 3 Claimed: No Online: No Reconnect count: 0 Banned By Cloud: No [root@host netdata]# netdata -v netdata v1.36.1 [root@host netdata]# netdata -W buildinfo Version: netdata v1.36.1 Configure options: '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--program-prefix=' '--disable-dependency-tracking' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--localstatedir=/var' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--enable-plugin-freeipmi' '--with-bundled-protobuf' '--with-zlib' '--with-math' '--with-user=netdata' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic' 'LDFLAGS=-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' 'CXXFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig' Install type: custom Features: dbengine: YES Native HTTPS: YES Netdata Cloud: YES ACLK Next Generation: YES ACLK-NG New Cloud Protocol: YES ACLK Legacy: NO TLS Host Verification: YES Machine Learning: YES Stream Compression: NO Libraries: protobuf: YES (bundled) jemalloc: NO JSON-C: YES libcap: YES libcrypto: YES libm: YES tcalloc: NO zlib: YES Plugins: apps: YES cgroup Network Tracking: YES CUPS: NO EBPF: NO IPMI: YES NFACCT: NO perf: YES slabinfo: YES Xen: NO Xen VBD Error Tracking: NO Exporters: AWS Kinesis: NO GCP PubSub: NO MongoDB: NO Prometheus Remote Write: YES [root@host netdata]# netdatacli aclk-state ACLK Available: Yes ACLK Version: 2 Protocols Supported: Protobuf Protocol Used: Protobuf MQTT Version: 3 Claimed: No Online: No Reconnect count: 0 Banned By Cloud: No [root@host netdata]# uname -a Linux host 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ``` ## What I expected to happen Housekeeping keeps the /var/cache/netdata/dbengine directory at a maximum size of the configuration parameter; 256M. ---
**Author:** ![Manolis\_Vasilakis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/manolis_vasilakis/32/820_2.png) [@Manolis\_Vasilakis](https://community.netdata.cloud/u/Manolis_Vasilakis)\ **Post date:** [January 5, 2023, 3:02pm UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/2 "2023-01-05T15:02:54Z")
Hi @svdb thanks for the report. Indeed the limit there can be exceeded if the metrics collected are a lot… Can you please post a screenshot of the chart `Netdata dbengine page cache statistics (netdata.page_cache_stats)` ? Esp. interested for the dimension `used_by_collectors`. Can you also perhaps update one of those agents to 1.37.1 and observe it’s behaviour? Thanks ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [January 6, 2023, 9:43am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/3 "2023-01-06T09:43:20Z")
Hi Manolis, thanks for the reply. I’ve attached screenshots of the metrics you requested, plus the Zabbix disk space graph for the /var partition. These nodes unfortunately only have about a day’s worth of metrics. I’m upgrading one of the nodes to 1.37.1 and will report the findings over the weekend. ![Screenshot from 2023-01-06 09-44-31](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/3/3037b50f315062eb47f28a6e9b7cdd6623330bb8.png) ![Screenshot from 2023-01-06 09-45-04](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/a/abca0a3afa0f1b53090ba3d5e87a2e4a80242307.png) ![Screenshot from 2023-01-06 09-45-37](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/1/100e0dcdf6e3a4d21ca13c46c6f90b500bc029b5.png) ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [January 6, 2023, 9:52am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/4 "2023-01-06T09:52:06Z")
```plaintext ]# tree -hsugpDQ /var/cache/netdata/ "/var/cache/netdata/" ├── [-rw-r----- netdata netdata 4.4M Jan 2 9:19] "anomaly-detection.db" ├── [-rw-r----- netdata netdata 16K Nov 25 13:40] "context-meta.db" ├── [-rw-r----- netdata netdata 32K Dec 28 20:11] "context-meta.db-shm" ├── [-rw-r----- netdata netdata 72K Dec 28 20:11] "context-meta.db-wal" ├── [drwxrwx--- netdata netdata 12K Jan 6 9:50] "dbengine" │ ├── [-rw------- netdata netdata 13M Jan 2 15:06] "datafile-1-0000000414.ndf" │ ├── [-rw------- netdata netdata 13M Jan 2 17:06] "datafile-1-0000000415.ndf" │ ├── [-rw------- netdata netdata 13M Jan 2 19:39] "datafile-1-0000000416.ndf" │ ├── [-rw------- netdata netdata 13M Jan 2 21:39] "datafile-1-0000000417.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 0:12] "datafile-1-0000000418.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 2:46] "datafile-1-0000000419.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 4:28] "datafile-1-0000000420.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 6:45] "datafile-1-0000000421.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 9:18] "datafile-1-0000000422.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 11:35] "datafile-1-0000000423.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 13:17] "datafile-1-0000000424.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 15:17] "datafile-1-0000000425.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 16:59] "datafile-1-0000000426.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 18:59] "datafile-1-0000000427.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 21:15] "datafile-1-0000000428.ndf" │ ├── [-rw------- netdata netdata 13M Jan 3 23:32] "datafile-1-0000000429.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 1:48] "datafile-1-0000000430.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 4:05] "datafile-1-0000000431.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 5:48] "datafile-1-0000000432.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 7:47] "datafile-1-0000000433.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 9:46] "datafile-1-0000000434.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 11:28] "datafile-1-0000000435.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 13:45] "datafile-1-0000000436.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 15:44] "datafile-1-0000000437.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 17:44] "datafile-1-0000000438.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 19:43] "datafile-1-0000000439.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 22:00] "datafile-1-0000000440.ndf" │ ├── [-rw------- netdata netdata 13M Jan 4 23:59] "datafile-1-0000000441.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 2:33] "datafile-1-0000000442.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 4:32] "datafile-1-0000000443.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 6:32] "datafile-1-0000000444.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 8:14] "datafile-1-0000000445.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 9:57] "datafile-1-0000000446.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 11:56] "datafile-1-0000000447.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 14:13] "datafile-1-0000000448.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 16:12] "datafile-1-0000000449.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 18:12] "datafile-1-0000000450.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 20:11] "datafile-1-0000000451.ndf" │ ├── [-rw------- netdata netdata 13M Jan 5 22:28] "datafile-1-0000000452.ndf" │ ├── [-rw------- netdata netdata 13M Jan 6 0:28] "datafile-1-0000000453.ndf" │ ├── [-rw------- netdata netdata 13M Jan 6 2:44] "datafile-1-0000000454.ndf" │ ├── [-rw------- netdata netdata 13M Jan 6 4:43] "datafile-1-0000000455.ndf" │ ├── [-rw------- netdata netdata 13M Jan 6 6:43] "datafile-1-0000000456.ndf" │ ├── [-rw------- netdata netdata 13M Jan 6 8:59] "datafile-1-0000000457.ndf" │ ├── [-rw------- netdata netdata 12M Jan 6 10:49] "datafile-1-0000000458.ndf" │ ├── [-rw------- netdata netdata 1.0M Jan 2 15:06] "journalfile-1-0000000414.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 2 17:06] "journalfile-1-0000000415.njf" │ ├── [-rw------- netdata netdata 1.1M Jan 2 19:39] "journalfile-1-0000000416.njf" │ ├── [-rw------- netdata netdata 2.5M Jan 2 21:39] "journalfile-1-0000000417.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 3 0:12] "journalfile-1-0000000418.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 3 2:46] "journalfile-1-0000000419.njf" │ ├── [-rw------- netdata netdata 2.4M Jan 3 4:28] "journalfile-1-0000000420.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 3 6:45] "journalfile-1-0000000421.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 3 9:18] "journalfile-1-0000000422.njf" │ ├── [-rw------- netdata netdata 1.1M Jan 3 11:35] "journalfile-1-0000000423.njf" │ ├── [-rw------- netdata netdata 2.6M Jan 3 13:17] "journalfile-1-0000000424.njf" │ ├── [-rw------- netdata netdata 960K Jan 3 15:17] "journalfile-1-0000000425.njf" │ ├── [-rw------- netdata netdata 896K Jan 3 16:59] "journalfile-1-0000000426.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 3 18:59] "journalfile-1-0000000427.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 3 21:15] "journalfile-1-0000000428.njf" │ ├── [-rw------- netdata netdata 2.9M Jan 3 23:32] "journalfile-1-0000000429.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 4 1:48] "journalfile-1-0000000430.njf" │ ├── [-rw------- netdata netdata 1.1M Jan 4 4:05] "journalfile-1-0000000431.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 4 5:48] "journalfile-1-0000000432.njf" │ ├── [-rw------- netdata netdata 2.9M Jan 4 7:47] "journalfile-1-0000000433.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 4 9:46] "journalfile-1-0000000434.njf" │ ├── [-rw------- netdata netdata 896K Jan 4 11:28] "journalfile-1-0000000435.njf" │ ├── [-rw------- netdata netdata 1.1M Jan 4 13:45] "journalfile-1-0000000436.njf" │ ├── [-rw------- netdata netdata 3.2M Jan 4 15:44] "journalfile-1-0000000437.njf" │ ├── [-rw------- netdata netdata 960K Jan 4 17:44] "journalfile-1-0000000438.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 4 19:43] "journalfile-1-0000000439.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 4 22:00] "journalfile-1-0000000440.njf" │ ├── [-rw------- netdata netdata 3.3M Jan 4 23:59] "journalfile-1-0000000441.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 5 2:33] "journalfile-1-0000000442.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 5 4:32] "journalfile-1-0000000443.njf" │ ├── [-rw------- netdata netdata 1020K Jan 5 6:32] "journalfile-1-0000000444.njf" │ ├── [-rw------- netdata netdata 3.3M Jan 5 8:14] "journalfile-1-0000000445.njf" │ ├── [-rw------- netdata netdata 908K Jan 5 9:57] "journalfile-1-0000000446.njf" │ ├── [-rw------- netdata netdata 976K Jan 5 11:56] "journalfile-1-0000000447.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 5 14:13] "journalfile-1-0000000448.njf" │ ├── [-rw------- netdata netdata 3.6M Jan 5 16:12] "journalfile-1-0000000449.njf" │ ├── [-rw------- netdata netdata 992K Jan 5 18:12] "journalfile-1-0000000450.njf" │ ├── [-rw------- netdata netdata 1.0M Jan 5 20:11] "journalfile-1-0000000451.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 5 22:28] "journalfile-1-0000000452.njf" │ ├── [-rw------- netdata netdata 2.7M Jan 6 0:28] "journalfile-1-0000000453.njf" │ ├── [-rw------- netdata netdata 2.1M Jan 6 2:44] "journalfile-1-0000000454.njf" │ ├── [-rw------- netdata netdata 972K Jan 6 4:43] "journalfile-1-0000000455.njf" │ ├── [-rw------- netdata netdata 1016K Jan 6 6:43] "journalfile-1-0000000456.njf" │ ├── [-rw------- netdata netdata 1.2M Jan 6 8:59] "journalfile-1-0000000457.njf" │ └── [-rw------- netdata netdata 3.7M Jan 6 10:46] "journalfile-1-0000000458.njf" ├── [-rw-r----- netdata netdata 134M Jan 6 5:22] "netdata-meta.db" ├── [-rw-r----- netdata netdata 32K Jan 6 8:19] "netdata-meta.db-shm" └── [-rw-r----- netdata netdata 15M Jan 6 7:40] "netdata-meta.db-wal" 1 directory, 97 files ``` ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [January 17, 2023, 9:18am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/5 "2023-01-17T09:18:42Z")
Here’s the node we upgraded: ```plaintext [root@host ~]# cd /var/cache/netdata/ [root@host netdata]# netdata -v netdata v1.37.1 [root@host netdata]# du -h 81M ./dbengine-tier1 542M ./dbengine 24K ./dbengine-tier2 974M . [root@host netdata]# curl -s localhost:19999/netdata.conf | grep dbengine dbengine disk space MB = 256 # mode = dbengine # dbengine page cache with malloc = yes # dbengine page cache size MB = 32 # dbengine multihost disk space MB = 256 # dbengine page fetch timeout secs = 3 # dbengine page fetch retries = 3 # dbengine page descriptors in file mapped memory = no # dbengine tier 1 page cache size MB = 16 # dbengine tier 1 multihost disk space MB = 128 # dbengine tier 1 update every iterations = 60 # dbengine tier 1 backfill = new # dbengine tier 2 page cache size MB = 8 # dbengine tier 2 multihost disk space MB = 64 # dbengine tier 2 update every iterations = 60 # dbengine tier 2 backfill = new # dbengine pages per extent = 64 ``` Since the upgrade to 1.37.1, disk usage of the /var partition keeps increasing like this: ![Screenshot from 2023-01-17 09-52-08](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/6/6f93ebb49c0e73925320e264705be0ad23c7919f.png) ![Screenshot from 2023-01-17 10-15-13](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/a/a5a10c5a7a54f4cfd74884113cbec85a4bc4f833.png) ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [January 25, 2023, 10:08am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/6 "2023-01-25T10:08:28Z")
@Manolis_Vasilakis is there any other information you need? ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [February 2, 2023, 8:52am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/7 "2023-02-02T08:52:49Z")
@ilyam8 could you possibly take a peek at this? ---
**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\ **Post date:** [February 2, 2023, 10:12am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/8 "2023-02-02T10:12:35Z")
Hi, @svdb. There have been really a lot of changes in dbengine since v1.37.1 (can say it was rewritten). I think you either try the latest nightly or wait for v1.38.0 (which will happen early next week). ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [February 2, 2023, 10:23am UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/9 "2023-02-02T10:23:05Z")
Thanks for the reply @ilyam8! I’ll wait for the release of v1.38.0 and report back with results. ---
**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\ **Post date:** [February 2, 2023, 12:32pm UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/10 "2023-02-02T12:32:08Z")
We found the problem, fixed in [DBENGINE v2 - bug fixes by ktsaou · Pull Request #14413 · netdata/netdata · GitHub](https://github.com/netdata/netdata/pull/14413). ---
**Author:** ![svdb](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/svdb/32/2506_2.png) [@svdb](https://community.netdata.cloud/u/svdb)\ **Post date:** [February 2, 2023, 12:50pm UTC](https://community.netdata.cloud/t/dbengine-directory-growing-despite-configured-disk-usage-limits/3703/11 "2023-02-02T12:50:39Z")
That’s great! I’ll still report back to confirm whether this solves the issue.