Hello, I had that same problem a month ago: a Zope 7.4 instance turning on a Solaris 9 with a 2.7 Gb Data.fs file, (hypo.ge.ch:8080 is for schools of secondary degrees in Geneva, I introduced zope there a few years ago and it meets a great success among teachers and schools but our base starts to grow big and we are encountering big problems to manage it with very little resources !) On saturday evening there has been a failure that required my intervention, I stopped zope and tried out the fsrecover script. Everything went OK and there had been no error found by fsrecover (?). I restarted Zope removing the Data.fs.index (I noticed that often Zope wouldn't start because of discreapencies between Data.fs and Data.fs.index => I wonder if it is not ZSync that does that mess?) It restarted OK, but all that has been made for 2 weeks was gone !!! Loking at the log to find out why, I saw in the event.log a lot of ERRORs of that kind: 2005-03-11T23:08:04 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 213.3.93.136:189 89 at 0x77bf828 channel#: 167268 requests:> (socket.error:(11, 'Resource temporarily unavailable') [/usr/local/lib/python2.3/asynchat.py|handle_ read|88] [/prd/data/Zope/var/zope2.7.4/lib/python/ZServer/medusa/http_server.py|recv| 423] [/usr/local/lib/python2.3/asyncore.py|recv|356]) Does anyone know, what does that mean and could it be the problem I have in this configuration? Dieter Mauer told me that after each transaction zope writes into the Data.fs, how can it be that I have a base with 2 weeks of missing data from the moment I do a restart? Thank you for your help, folks, I get despaired with that problem (many teachers lose hours of their work) serge