On Sun, 26 Nov 2000, Robert Collins wrote:
> so the cleanup code could that calls doublecheck could call it on a new file
> being written, thus causes a problem.
Can you be more specific. What bad things are going to happen in this
case? Unlinking an open file is not bad (at least not on unix) because
any other thread that has the file open for reading and writing can
continue reading and writing.
> Finally is there any reason the storeCleanup code can't be part of the
> rebuild? Now the disk checking is a background task, the Cleanup routine
> just counts the file sizes and sets the VALIDATED bit.
Actually I was thinking that storeCleanup() can probably go away
entirely. The VALIDATED bit is less useful now that the
swapin code is more robust (checking size, MD5, URL).
Also I think there is really no difference between a clean and
dirty rebuild, so that can disappear as well.
Received on Thu Nov 30 2000 - 15:41:47 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:01 MST