Help! Did somebody experienced the same issue?
After the last update my rootf ist completely full. After a while the Installation isnt accsesible due to the lack of space.
What to do?!
Version
7.7.6-1 (Sandworm)
Kernel
Linux 6.12.22+bpo-amd64
Help! Did somebody experienced the same issue?
After the last update my rootf ist completely full. After a while the Installation isnt accsesible due to the lack of space.
What to do?!
Version
7.7.6-1 (Sandworm)
Kernel
Linux 6.12.22+bpo-amd64
hi this has nothing to do with Nextcloud - any Linux OS stops working if rootfs is full. each search engine will show lot of discussions on this topic.
Thanks for the quick reply. Yes i know that. Sorry i forget the circumstances that caused the problem. My setup is a ugreen dxp4800+ with PVE8.4.1. 4 HDD are physically reached trough to an VM with OMV7.
I always have had 24% space left on the drive. After the last update by OMV the space vanished to zero. i have a nextcloud and a immich installation in docker within OMV, but there are no remarkable actions done recently.
This VM resides on a virtual space with 32GB. This is the bottleneck i had experienced now.
The reason i asked is that i do not know the reason causing the problem.
First i want to know a secure workaround for my situation.
Second i want to avoid this in future.
Thank you in advance
After a short search i found out that the mariaDB LOG root@openmediavault:/data/docker/appdata/nextcloud/mariadb/config/log/mysql was filled up to 16GB - is that normal? Can i move the mariaDB to another volume or clean it ?
“all” databases write a “transaction log” (google for details) which is intended to ensure atomic operations - each write operation will be written on the disk twice and in case of crash it is possible to recover some certain valid state. It looks massive database change happened and caused many write operations which in turn cause transaction logs to grow.
mature DBMS like MariaDB offer ways to recover from fail condition with or without data loss (even very granular e.g. last transaction file before crash) - you better search MariaDB forums and docs for answers.
If it works you would recommend to extend the storage and then try to start the DB first - depending on your preferences accepting some data loss - once it works you can proceed the log files as you want - move, delete, process…
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.