Thousands of zero size files in cache directory

pabbito
(@pabbito)

18 years, 3 months ago

My host provider informed me of a very annoying problem. My wordpress 2.0 generates thousands of zero size files in directory cache/userlogins and cache/users. Similar number files is also generated in system /tmp/. The number of files is do big that it causes “no space left on device” error and the sessions can’t be saved any more.

I didn’t noticed that kind of problem on WP1.5

What so big number of files is for?
And how can I configure it so that it stopped breaking the hosting down?
Can caching be switched off at all?

Viewing 13 replies - 1 through 13 (of 13 total)

Mark (podz)
(@podz)

18 years, 3 months ago

1. Who is your host ?

2. Yes it can be switched off.
You can disable caching (temporarily or permanently) by adding this line to your wp-config.php

define(‘DISABLE_CACHE’, true);

abrazell
(@abrazell)

18 years, 3 months ago

Just curious about the irony of thousands of “zero size files” and “no space left on device”. Someone is telling you the wrong thing.

One workaround is exactly as Podz indicates though. I have cache disabled on all my blogs so I can’t see what WP is actually generating on a normal basis without enabling and letting it run for awhile.

Thread Starter pabbito
(@pabbito)

18 years, 3 months ago

My host is http://www.futuro.pl
define('DISABLE_CACHE', true); – might be useful

I saw the error: Error code 28: No space left on device personaly while watching my site once or twice and the zero size files I can also see when I enter cache/userlogins for example. I found somewhere on this forum that the error cn also be generated by extremly big number of files in system tmp. My provider said the files in tmp comes form my wordpress.

How much switching off cache system can influence the performance of wordpress and my site? Is it worth using at all? Any experiences?

Claudio Simeone
(@mrbrown)

18 years, 3 months ago

Just curious about the irony of thousands of “zero size files” and “no space left on device”. Someone is telling you the wrong thing.

Yes, more exactly the problem is that all those empty files full all partition inodes, so the filesystem can’t create new files.

I had the same problem and I disabled the cache.

(sorry for my bad english)

abrazell
(@abrazell)

18 years, 3 months ago

Yes, more exactly the problem is that all those empty files full all partition inodes, so the filesystem can’t create new files.

THAT makes sense.

Thread Starter pabbito
(@pabbito)

18 years, 3 months ago

I had the same problem and I disabled the cache.

But it’s not the solution, maybe the cache is useful.
What one would need such a cache system that makes too much files? Is there a way to configure it properly?

Claudio Simeone
(@mrbrown)

18 years, 3 months ago

But it’s not the solution, maybe the cache is useful.

I know that the cache is useful, but I wasn’t able to solve, so I disabled 🙂

I suppose that’s a PHP configuration problem, especially Safe Mode set to On. Can you check if your PHP is running in safe mode?

Kassad
(@kassad)

18 years, 3 months ago

It is certainly not wp-cache problem.
The cache generates few and small files.

Databese error 28 is general in case of free or cheap hosts.
Little space left on hard disk, no one cares to clear it and certainly they are not top notch professionals either.

Thread Starter pabbito
(@pabbito)

18 years, 3 months ago

They are very professional and not so cheap. The files regenerates in that number during 2 days. And It is only caused by WP not any other scripts (I run a few)

wp-cache generates thousands of files (0 bytes) – I’ve seen it.

Can you check if your PHP is running in safe mode? – Yes, it is.

Claudio Simeone
(@mrbrown)

18 years, 3 months ago

It’s sure: it depends from Safe Mode set to on. Unfortunately, seems that there are no fixes to the problem.
The next version of WP (2.0.1), in fact, will disable the cache if PHP runs in safe mode.

Also check out this message from the WP Hackers Mailing List.

Thread Starter pabbito
(@pabbito)

18 years, 3 months ago

Thank you for the investigation. If it’s true it’s a pity that developers didn’t predicted it earlier.

Is it a feature of WP 2 or earlier versions also had that kind of problem?

Claudio Simeone
(@mrbrown)

18 years, 3 months ago

No, it’s only a problem of WP 2.0. Earlier versions don’t use a cache system, so there are no problems.

Thread Starter pabbito
(@pabbito)

18 years, 3 months ago

So there is a chance that developers will work on it later. It would be good if WP could make a tmp folder for itself when SaveMode is on, instead of using system tmp.