Hello, We are running an old version of mediawiki (1.24.2), and have noticed recently that overnight we are seeing that the disk utilisation is reaching nearly 100% for almost an hour. During the night, at different times, we run a database backup (mysqldump) and a database check (mysqlcheck). It turns out that these are causing the disk usage problem. In particular the database table 'objectcache' has nearly 500,000 entries. Whilst the table has an expiry date/time field for the records, all but about 10 of the records have the expiry date set to the year 2038! Looking at the key names for some of the records they seem to be of the form: 'SM:resourceloader:filter:minify-css:7:066ff155efe7761cc6472668436b9554'. My questions are: 1) Is it right that 'minify-css' records should have a very long expiry date (such that they are basically going to accumulate over time)? 2) The mediawiki docs say that it is possible to purge the table as required since the records will be recreated. Will this have any effect on someone who is using the wiki at the time the table is purged? Current plans are to modify our backup script to exclude the table, but include its 'structure' into the backup file. (Kudos to AmitP's answer at https://stackoverflow.com/questions/13593148/mysql-dump-exclude-some-table-… ). In addition, our database check script will perform a table purge beforehand if it is safe to do so. (Plans also include updating the mediawiki version!) Thanks, John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.a… This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.