On Oct 2, 2006, at 5:38 PM, Juan Pablo Giménez wrote:
I'm not blaming the zope team... zope is great!
but the real problem wasn't a deleted file... was a corrupted
file... and a sysadmin who doesn't read the log file...
but... if zope knows about the corrupted Data.fs, why keeps
writing into .tmp file?!
A diagram of that sentence might help:
"but... if zope knows about the corrupted Data.fs"... First of all,
do you know that Zope knew the file was corrupt? How do *you* know
it had been corrupted? And what does 'corrupt' mean? It seems like
even it it had been corrupted in some way (meaning, say, bytes inside
of it had been overwritten with garbage, for example), it wouldn't
matter, because apparently someone unlinked it so it's not anywhere
around to analyze. So I'm afraid nothing can be done without some
sort of backup copy or unless Zope is still running and you can get
at its file descriptor from within the /proc filesystem or something.
"why keeps writing into .tmp file?!" ... this is not meaningful to
the conversation, it'd be better just to leave this part of the
sentence above off.
In any case, I'm not sure there's anything we can do to help unless
you have a backup or unless Zope happens to still be running.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org