[Zope-dev] Crash & Burn with Zope 2.6.0a1 and ZEO 2.0a1

[Jeremy Hylton]

>>>>> "AS" == Andrew Sydelko <andrew@sydelko.org> writes:

  AS> On Tue, 18 Jun 2002 11:20:21 -0400 "Jeremy Hylton"
  AS> <jeremy@zope.com> wrote:
  >> >>>>> "AS" == Andrew Sydelko <andrew@sydelko.org> writes:
  >>
  AS> Trying Zope 2.6.0a1 and ZEO 2.0a1. The storage server seemed to
  AS> come up fine, but when trying to start the ZEO client it pretty
  AS> much sucked.
  >>
  >> It looks like you would have had the same problems without ZEO.
  >> It would be helpful if you could try running Zope without ZEO,
  >> just with FileStorage.

  AS> Hmm... The first time I copied the 3gig Data.fs over and tried
  AS> to start Zope a few times. After fiddling with the permissions
  AS> of the var directory it finally started, but the Data.fs was
  AS> only 2MB!

  AS> So I copied it again. And once again, the 3gig Data.fs is blown
  AS> away!  What am I doing wrong??? What are the permissions of the
  AS> "var" folder supposed to be? I'm starting Zope with:

It wouldn't surprise me if this is a completely unrelated problem.
Any chance that the python your using to test doesn't have large file
support?  Check by importing test.test_largefile.

We recently discovered that there's a bad interaction between ZODB and
Python without large file support running on a platform that supports
large files.  In this specific configuration, os.path.exists() returns
false for files >2 GB and ZODB creates a new Data.fs.

Jeremy