On 14/02/2008, at 8:11 AM, ALopez@xxxxxxxxxx wrote:
Because it didn't work either. Anytime I try (either through Zend's
install, MySQL's install, or directly from the command line in QSH)
the
following fails:
QOpenSys/usr/bin/tar -xf /tmp/mysql_i5os_install.tar. It will
start, but
inevitably it aborts with: "tar: 0511-197
mysql-5.0.45-i5os-power-64bit/bin/mysqld-debug: Cannot write data
extracted with the tar command. Thre is not enough space in the file
system."
Since I have close to a terabyte of free DASD, I'm at a loss. So
is Zend.
So is IBM. We're at V5R4M5 with all the latest PTF groups.
I thought this had been resolved in a previous append. Without
examining the code of tar I cannot be sure but this smacks of a
coding defect. My guess is that you have TOO MUCH free space. Why?
Because tar is checking the available free-space but (probably)
storing it in a too small value (e.g., short instead of int or int
instead of long long) therefore overflow occurs and the resulting
value indicates insufficient free-space even though that is not true.
You can prove this by creating dummy objects to consume lots of free
space. Something like:
CRTPF DUMMY/DUMMY00001 RCDLEN(32767) SIZE(2147483647) ALLOCATE(*YES)
repeated until sufficient space is consumed.
This sort of rubbish happened a lot in the early days of DOS and Unix
as drive sizes increased. I thought we were past that by now.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.