Old deleted files not being purged by cron job and not showing in web interface either

Server
1

Running version 10.15.0.2 on AlmaLinux cloud server with config:

  'trashbin_retention_obligation' => '30, 120',
  'versions_retention_obligation' => '30, 120',

and the cron job runs only for one heavy user (who doesn’t have a quota). The version purge seems to be working OK - when I look at the files_version folder on disk and files_trashbin/versions also looks fine, but if I look at files_trashbin/files on disk, there are a lot of old files (some dating back 4 years) which are taking up a load of space and which I’d like to delete. If I look at deleted files via the web UI and sort by date, I only see recently deleted files (looks like 30 days).

My guess is that somehow the filesystem has gotten out of sync with the DB? I know that there’s a occ files:scan command which might resync the filesystem with the DB (not sure if that also works for deleted files as well though?), but I’m wondering if the suffix on the filename is some kind of deleted timestamp and if I could just use that to manually delete the old files?

-rw-r--r-- 1 owncloud owncloud     8777925 Jun 20  2021 'BELEUN[0010].d1753730776'
-rw-r--r-- 1 owncloud owncloud     8762826 Jun 18  2021 'BELEUN[0008].d1753730773'
-rw-r--r-- 1 owncloud owncloud     8610794 Jun 14  2021 'BELEUN[0006].d1753730771'
-rw-r--r-- 1 owncloud owncloud     8013115 Jun 11  2021 'BELEUN[0004].d1753730768'
-rw-r--r-- 1 owncloud owncloud     7423519 Jun  5  2021 'BELEUN[0002].d1753730765'
-rw-r--r-- 1 owncloud owncloud     4440584 Jun  4  2021 'BALESE[0004].d1755296723'
-rw-r--r-- 1 owncloud owncloud     4438611 Jun  2  2021 'BALESE[0002].d1755296723'
2

Answering my own question! Yes it looks like that is a Unix timestamp, and the oldest one in my list of files is 1753189210 => 22nd July 2025, so it looks like the cron job is actually working as expected :slight_smile: and it’s just that those old files have only recently been deleted.

1 Like