I'm trying to fix bug #1511, crashes on NVFS devices with large images.
The following issue seems to be a problem. Plucker's image cache
itself gets cached in the NVFS dbcache. Our MemHeapFreeBytes() call
returns the amount of space left in the "storage heap". However, this
apparently does not take into account the amount of write-pending data
in dbcache. This means that if we keep on adding data to the image
cache until MemHeapFreeBytes() falls below our safe limit, we will end
up with an almost full hidden flash drive, AND a bunch of write-pending
data in dbcache. I don't know if NVFS lets one overstep the total
available space in this way, but whether it does or not, problems will
result.
So, question: How do we find out how much space there _really_ is in the
storage heap: i.e., amount of space in the hidden flash drive minus the
write pending data in the dbcache? Does anybody know?
Alex
_______________________________________________
plucker-dev mailing list
[email protected]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
