We have a situation where the client scanned color documents in 24 bit color, consuming a year's worth of storage in a single day.  We have built a utility similar to the 8.1 Image Conversion Utility, also using Lead.  We can convert the 24 bit images to 8 bit images in place, overwriting the original images.  This sleight of hand works fine, as far as viewing the pages afterwards.  When we update dbo.doc.img_size, the Admin Console reports the Volume's size properly. 

However, the values in dbo.vol.cursize (current size) and dbo.vol.curdisksize (current size on disk) never seem to go down, even after deleting documents from the system, purging the recycle bin, and restarting the server so it can take care of garbage collection.  This must have impact on roll over calculations.  So:  Why does this value never get adjusted downward, and is there any harm in updating this to a correct value?

TIA