Re: Packing, again

On Sunday 05 Sep 2004 22:29, Richard Waid wrote:

> Ah, that's what I had thought. Does that mean if I restore the one file
> it's complaining about missing, it might also fix the problem?

Yes. 

> > *all* of these problems can be fixed by repeating the pack and allowing
> > it to finish. However you do need the pack time to be no longer than in
> > the interrupted pack. It is possible for the second pack in the following
> > scenario to fail.... does this apply to you?
> >
> > a. many things were deleted 2 days ago
> > b. start packing keeping 1 day of history. interrupt it during phase 4.
> > c. start packing keeping 3 days of history.
> >
> > To resolve these problem, you need to pack keeping 1 day of history ...
> > the same setting as the pack that was interrupted in step b.
>
> Hmm. As previously discussed (and to be remedied in all future packs
> here), I didn't actually keep history, so how would I remedy using this?

the history I refer to above is the same sort of history that FileStorage 
packing keeps, that you set using Zope's gui "keep X days of history". 
history that can be seen using undo.

_not_ delay_delete history.

On Sunday 05 Sep 2004 22:18, Richard Waid wrote:
> > Pass 4 simultaneously:
> > 1. renames files to -deleted if the mark/sweep logic has found them to be
> > unnecessary, and
> > 2. unlinks -deleted files that are older than the delete_delay.
> >
> > or, if delete_delay is zero, it unlinks them direct.
>
> That was my understanding. Perhaps the behaviour of delay_delete should
> be changed (for robustness) to the same as the normal case?

Suppose that was moved to pass 5 - what robustness would you gain? 
Interrupting pass 4 would still cause the problem that has affected you,  but 
you would have the option of renaming the -deleted files. In any case that 
problem could be also fixed by restarting the pack and allowing it to finish, 
as I describe above. The cost is in time - pass 5 would take as long as pass 
4 does today.

Maybe a better option would be for pass 4 to determine which files need 
deleting, but to not actually delete them. That deletion list could get 
replayed before a subsequent pack. That should eliminate this problem, but 
does suffer from scalability problems for packs that remove lots of files.







-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click