Disk quota negative bytes free

CodeHaus Comment From: aaime - Time: Sun, 3 Feb 2013 05:02:49 -0600
---------------------
<p>I believe I've seen this happen when tiles were manually deleted from the disk (without using a truncate against the tile layer)</p>

CodeHaus Comment From: jonathan_wcc - Time: Mon, 4 Feb 2013 04:59:08 -0600
---------------------
<p>When I upgraded to 2.3beta1 the issue went away, though that may be from my "backup" process where I deleted some stuff from the gwc directory.</p>

<p>For me at least I can't replicate it this way. I've deleted the directory/tiles with GeoServer running and not-running but that didn't occur again.

But I had manually deleted some tiles when this initial issue occurred.</p>

CodeHaus Comment From: groldan - Time: Wed, 6 Feb 2013 11:15:23 -0600
---------------------
<p>Closing as not a bug. If you manually delete tiles from disk you can either:</p>
<ul class="alternate" type="square">
<li>If you deleted a whole layer cache, you can restart geoserver so the diskquota startup thread catches up with the missing layer and removes it from its database</li>
<li>Otherwise just delete de &lt;data dir&gt;/gwc/diskquota_page_store directory and let the usage stats be recreated at geoserver startup.</li>
</ul>

CodeHaus Comment From: jonathan_wcc - Time: Fri, 8 Mar 2013 10:13:32 -0600
---------------------
<p>I don't think that's the only cause. Just replicated it with no manual file deletion.

Start with a deleted quota and restarted Geoserver.

Disk quota is correct.

"Emptied" one of the two caches using the interface, and it goes to 0.0Byes (see <a href="http://jira.codehaus.org/browse/GEOS-5699" class="external-link" rel="nofollow">http://jira.codehaus.org/browse/GEOS-5699</a>).

After the quota is updated it remains at 0.0Bytes.</p>

<p>BUT, if I then change the frequency to 1 second, I get:

"Using -1,259,126,784.0 B of a maximum 5.0 GB"

or:

"Using -3,577,909,248.0 B of a maximum 5.0 GB"

I suspect its because I'm submitting this form rather than being specific to the frequency.</p>

<p>Or some other number. This appears to be distinct from 5699, so re-opening.</p>

This issue is fixed by this pull requests in GWC:

• https://github.com/GeoWebCache/geowebcache/pull/484

• https://github.com/GeoWebCache/geowebcache/pull/485

• https://github.com/GeoWebCache/geowebcache/pull/486

Associated GWC issue:

• https://github.com/GeoWebCache/geowebcache/issues/483

Clarification for those upgrading. If yours is already corrupted:

• Stop Geoserver

• Go to the data directory, get into "gwc/diskquota_page_store_h2" and remove all files

• Start again (GeoServer will rebuild the quota db, migth take a while), then you're good to go