I'm fairly well versed on the inner workings of Zope, but yesterday I've
run into a problem that I can grasp.
First, some background on what I'm doing.
I've got a 200GB Data.fs file which I'm splitting up into multiple
storages. The way I'm doing this is to create a zope instance which
mounts a new storage and the old storage and then a python script
connects to the application and uses a modified version of manage_clone
(which maintains ownership) to copy content into the new storage.
This works correctly for most things, but yesterday I tried to move a
folder with about 3.1GB of stuff in it.
On a side note, I ran into an issue with running out of /tmp space
during the clone. The _getCopy method of CopySourse exports an object to
a tempfile and then imports it to create the copy. When copying
something larger than available tmp space zope crashes. I worked around
this by explicitly setting tempfile.tempdir to somewhere with plenty of
free space. There may be an environment variable to do this as well.
Just an FYI.
Anyway, here's what I see. The copy starts, a tempfile is created (on
the client) and grows to the appropriate size (3.1GB). Then, a
Data.fs.temp appears on the new server and grows to the appropriate
size. However, when my script tries to commit the transaction I get an
Traceback (most recent call last):
File "./migrate_site.py", line 45, in ?
line 325, in commit
line 427, in _commitResources
line 744, in tpc_vote
s = vote(transaction)
line 1004, in tpc_vote
line 262, in vote
return self.rpc.call('vote', trans_id)
699, in call
raise inst # error raised by server
I don't seem to have any space issues on any devices, and the process
works for smaller site. Any input would be greatly appreciated.
Web Services Coordinator
Engineering Computer Network
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -