New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
cagefs related info
mysqld creating bin files in cagefs which is consuming around 550Gb Disk space can u delete these binary files is its safe to delete such files
Using DIRECTADMIN
1.0 GiB [######### ] binlog.000427
1.0 GiB [######### ] binlog.000556
1.0 GiB [######### ] binlog.000432
1.0 GiB [######### ] binlog.000425
1.0 GiB [######### ] binlog.000257
1.0 GiB [######### ] binlog.000534
1.0 GiB [######### ] binlog.000429
1.0 GiB [######### ] binlog.000476
1.0 GiB [######### ] binlog.000530
1.0 GiB [######### ] binlog.000319
1.0 GiB [######### ] binlog.000438
1.0 GiB [######### ] binlog.000531
1.0 GiB [######### ] binlog.000590
1.0 GiB [######### ] binlog.000459
1.0 GiB [######### ] binlog.000553
1.0 GiB [######### ] binlog.000430
1.0 GiB [######### ] binlog.000587
1.0 GiB [######### ] binlog.000451
1.0 GiB [######### ] binlog.000557
1.0 GiB [######### ] binlog.000498
1.0 GiB [######### ] binlog.000247
1.0 GiB [######### ] binlog.000569
1.0 GiB [######### ] binlog.000367
1.0 GiB [######### ] binlog.000448
1.0 GiB [######### ] binlog.000452
1.0 GiB [######### ] binlog.000437
Comments
@MikePT @Da_Mark can help ?
https://www.cloudlinux.com/forum/forum11/how-can-i-safely-exclude-all-mysql-databases-from-cagefs
Seems to be just mounted, however, to confirm, you may want to open a ticket with CloudLinux, they're really fast getting back to us.
already submitted ticket there waiting for their response
That's still mounted, which seems normal, but, best to confirm.
It might just be regular MySQL binlogs (binary logs) rather than anything specific to CloudLinux. Binary logs are logs of all writes performed to your MySQL server. They're used for replication and for data recovery. See https://dev.mysql.com/doc/internals/en/binary-log-overview.html
How many queries is your server running? A lot of writes will result in large binlogs. Check how many days of binlogs you're storing:
then:
If you don't need older binlogs you can purge them: https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html
eg this will delete all binlogs older than 24 hours:
You can also reduce the
binlog_expire_logs_seconds
orexpire_logs_days
setting to keep a smaller number of binlogs.Do not manually delete binlog files - Use the
PURGE BINARY LOGS
command.mo> @Daniel15 said:
THANKS CL Team was solved this issue with the same guide
Its not safe to just delete them.
Definitely not. That is what PURGE BINARY LOGS is for. 🤘