On 30 June 2014 10:32, Frédéric Iterbeke <frederic.iterb...@ugent.be> wrote:
> Op 30/06/2014 9:30, Alessandro Pisa schreef:
>> I have a ~70Gb Data.fs that does not pack anymore.
>> When I pack it it creates a ~8GB Data.fs.pack, then it evaluates thi
>> as True, removes, the Data.fs.pack and returns.
>> The same happens with ZODB-3.10.5 and using pack-gc = false.
>> In every permutation I tried the produced Data.fs.pack files have the
>> same checksum.
>> Does anybody have some hints?
>> What I am trying to do:
>> - comment the Data.fs.pack removing.
>> - use that file as a new Data.fs
> Well, 70 Gb Data.fs is pretty big. But not impossible afaik.
> If you set pack-gc = false it's normal that nothing is removed.
Setting or unsetting it doesn't change the produced Data.fs.pack (it
has the same md5sum).
Anyway the pack time considerably reduces (from 4 hours to 25 minutes).
> If you think the code is doing something wrong and you would like to try
> packing anyway, I would suggest you just comment the entire if in the
> fspack.py code and try running this version. If I read the code correctly,
> this would force (at least trying) a pack in any case, assuming
The problem is that the Data.fs pack produced contains transactions
until Jun 1st.
Anyway I will try this also.
> I'm not guaranteeing anything and I'm just a zodb user though ;) And
> remember to use a copy of your data when doing stuff like this ;)
Yeah, I am working on a copy, of course :p
> Good luck!
Thanks, I need it ;)
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org