[ZODB-Dev] HOWTO recover from Data.fs.tmp
Russ Ferriday
russf at topia.com
Mon Oct 2 14:07:31 EDT 2006
But for an app to be writing into thin air without complaining -
THAT's a bug!
Even having a backup of the Data.fs would not help!
Not picking on zope, but if that's what's happening it has to be
called a bug.
--r
On 2 Oct 2006, at 19:00, Benji York wrote:
> Juan Pablo Giménez wrote:
>> El lun, 02-10-2006 a las 19:41 +0200, Dieter Maurer escribió:
>>> Juan Pablo Giménez wrote at 2006-9-29 18:23 -0300:
>>> > I have,
>>> >
>>> > Plone 2.1.2, > Zope (Zope 2.8.6-final, python
>>> 2.3.5, linux2), > Python 2.3.5 (#1, Apr 11 2006, 16:55:30)
>>> [GCC 3.3.5 (Debian
>>> > 1:3.3.5-13)],
>>> > >
>>> > For some reason zope stop writing at Data.fs about a week
>>> ago. Now i
>>> >have a Data.fs with 1 week older data and a Data.fs.tmp with, I
>>> hope,
>>> >the new data...
>>> I fear you are out of luck...
>>>
>>> "Data.fs.tmp" usually only contains the last transaction (although,
>>> it may not free unused space at the end).
>> but... that's a bug... why zope keep writing in .tmp file if we
>> can't recover nothing from there?!?!...
>
> Why is it a bug? A .tmp file is just that, temporary. It's not a
> backup.
> --
> Benji York
> Senior Software Engineer
> Zope Corporation
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
>
> ZODB-Dev mailing list - ZODB-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zodb-dev
More information about the ZODB-Dev
mailing list