Importing -> Disk full
Hi, I'm trying to import a *.zexp File into Zope 2.6 which lies in /opt on a RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas? regards Lars
On Wed, Oct 23, 2002 at 10:11:17AM +0200, Lars H. Korte wrote:
Hi,
I'm trying to import a *.zexp File into Zope 2.6 which lies in /opt on a RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas?
What partition does your '/tmp' directory sit on? It's possible that Zope needs to create temporary files and runs out of space in /tmp. hth Ralf Mattes
regards Lars
_______________________________________________ Zope-DB mailing list Zope-DB@zope.org http://lists.zope.org/mailman/listinfo/zope-db
Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:11:17AM +0200, Lars H. Korte wrote:
Hi,
I'm trying to import a *.zexp File into Zope 2.6 which lies in /opt on a RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas?
What partition does your '/tmp' directory sit on? It's possible that Zope needs to create temporary files and runs out of space in /tmp.
hth
Ralf Mattes
regards Lars
Hi, that was my first idea, too. But taking a look into '/tmp' during the import process, there are NO files that were created? I could not find any! Can't I find something in the Zope-Sources? regards Lars
that was my first idea, too. But taking a look into '/tmp' during the import process, there are NO files that were created? I could not find any!
Temporary files are frequently unlinked after being opened to ensure the space they consume will be released when the file handle is closed (this avoids race conditions as well). Use lsof(8) or fuser(1) or 'ls -l /proc/<pid>/fd' to identify if zope is keeping files open in /tmp during the import. Or just read the source. Assuming that is the problem, your system partitions aren't set up to meet your needs, you need to re-partition. -- Jamie Heilman http://audible.transient.net/~jamie/ "Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution." -Sathington Willoughby
On Wed, Oct 23, 2002 at 10:59:38AM +0200, Lars H. Korte wrote:
Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:11:17AM +0200, Lars H. Korte wrote:
Hi,
I'm trying to import a *.zexp File into Zope 2.6 which lies in /opt on a RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas?
What partition does your '/tmp' directory sit on? It's possible that Zope needs to create temporary files and runs out of space in /tmp.
hth
Ralf Mattes
regards Lars
Hi,
that was my first idea, too. But taking a look into '/tmp' during the import process, there are NO files that were created? I could not find any!
That doesn't mean anything. The classic Unix way of doing things like this is: - open a (temporary) file. - unlink (delete) it. <-- from here on the file is "invisible" - do your stuff - close the file <-- as soon as the file is closed it's inode can be reused by the OS. This is nice use of the semantics of Unix/Posix unlink: a file will stay arround as long as there is a file descriptor pointing at it.
Can't I find something in the Zope-Sources?
Most likely not - Zope uses Python that very likely uses '(3) mkstemp' or a similar libc function. Two _possible_ solutions (after checking that '/tmp' realy sits on a tight partition): - move '/tmp' to another partition (it should be possible by: 'cp -ar /tmp /opt/tmp && ln -s /opt/tmp /tmp') - start your Zope like this: $ export TMPDIR=/opt/tmp $ /etc/init.d/zope start # or whatever your zope startscript is .. hth Ralf Mattes
regards Lars
_______________________________________________ Zope-DB mailing list Zope-DB@zope.org http://lists.zope.org/mailman/listinfo/zope-db
Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:59:38AM +0200, Lars H. Korte wrote:
Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:11:17AM +0200, Lars H. Korte wrote:
Hi,
I'm trying to import a *.zexp File into Zope 2.6 which lies in /opt on a RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas?
What partition does your '/tmp' directory sit on? It's possible that Zope needs to create temporary files and runs out of space in /tmp.
hth
Ralf Mattes
regards Lars
Hi,
that was my first idea, too. But taking a look into '/tmp' during the import process, there are NO files that were created? I could not find any!
That doesn't mean anything. The classic Unix way of doing things like this is:
- open a (temporary) file. - unlink (delete) it. <-- from here on the file is "invisible" - do your stuff - close the file <-- as soon as the file is closed it's inode can be reused by the OS.
This is nice use of the semantics of Unix/Posix unlink: a file will stay arround as long as there is a file descriptor pointing at it.
Can't I find something in the Zope-Sources?
Most likely not - Zope uses Python that very likely uses '(3) mkstemp' or a similar libc function. Two _possible_ solutions (after checking that '/tmp' realy sits on a tight partition):
- move '/tmp' to another partition (it should be possible by: 'cp -ar /tmp /opt/tmp && ln -s /opt/tmp /tmp')
- start your Zope like this: $ export TMPDIR=/opt/tmp $ /etc/init.d/zope start # or whatever your zope startscript is ..
hth
Ralf Mattes
regards Lars
_______________________________________________ Zope-DB mailing list Zope-DB@zope.org http://lists.zope.org/mailman/listinfo/zope-db
Hi, thanks a lot, that helped!!!! regards Lars
I have the same problem when running under Win2K. When Zope 2.6.0 is on the C: drive Import works fine, however, when I have it on a different partition; i.e. G:, I get the "disk full" error. Any suggestions on fixing in Win2K? Garry Galinsky garry@galinsky.net (403) 667-4777 (403) 667-4744 Fax -----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org] On Behalf Of Lars H. Korte Sent: October 23, 2002 04:45 To: Le grande pinguin Cc: zope@zope.org Subject: [Zope] Re: [Zope-DB] Importing -> Disk full Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:59:38AM +0200, Lars H. Korte wrote:
Le grande pinguin schrieb:
On Wed, Oct 23, 2002 at 10:11:17AM +0200, Lars H. Korte wrote:
Hi,
I'm trying to import a *.zexp File into Zope 2.6 which lies in
/opt on a
RedHat 7.2. During the import process the filesystem mounted on / gets full !!! Why that? What does Zope do on /, when it's supposed to hold it's data in /opt ? How can I change this? I cannot change the capacity for / !!! Any Ideas?
What partition does your '/tmp' directory sit on? It's possible that Zope needs to create temporary files and runs out of space in /tmp.
hth
Ralf Mattes
regards Lars
Hi,
that was my first idea, too. But taking a look into '/tmp' during the import process, there are NO files that were created? I could not find any!
That doesn't mean anything. The classic Unix way of doing things like this is:
- open a (temporary) file. - unlink (delete) it. <-- from here on the file is "invisible" - do your stuff - close the file <-- as soon as the file is closed it's inode can be reused by the OS.
This is nice use of the semantics of Unix/Posix unlink: a file will stay arround as long as there is a file descriptor pointing at it.
Can't I find something in the Zope-Sources?
Most likely not - Zope uses Python that very likely uses '(3) mkstemp' or a similar libc function. Two _possible_ solutions (after checking that '/tmp' realy sits on a tight partition):
- move '/tmp' to another partition (it should be possible by: 'cp -ar /tmp /opt/tmp && ln -s /opt/tmp /tmp')
- start your Zope like this: $ export TMPDIR=/opt/tmp $ /etc/init.d/zope start # or whatever your zope startscript is ..
hth
Ralf Mattes
regards Lars
_______________________________________________ Zope-DB mailing list Zope-DB@zope.org http://lists.zope.org/mailman/listinfo/zope-db
Hi, thanks a lot, that helped!!!! regards Lars _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (4)
-
Garry Galinsky -
Jamie Heilman -
Lars H. Korte -
rm＠mh-freiburg.de