said:
> zip I/O error: Disk full
> zip error: Output file write failure (write error on zip file)
> errorlevel 14
Yep, zip does not have infinite capacity.
> where error 14 according to the manual is "error writing to a file"
It's possible zip is running out of virtual address space and the side
effect is that the I/O fails.
It's easy enough to use the OS/2 trace to watch the I/O done by zip.
Something like:
trace on /b:1024
trace on /n:zip.exe
trace on kernel(fs=pre+post)
zip
trace off
tracefmt
should let you see the failing I/O.
>but none of my disks are full (still have several GB of free space on the
>target drive) and usually the file zip is compressing at the time of the
>error is quite small.
All that says is it's not a file specific failure.
>I suppose zip could be reaching a 2 GB threshhold and "thinks" the disk
>is full. Anybody have any ideas on what I should look for?
Well you've got a couple of choices. You could grab the source code for
zip and debug the problem and, perhaps develop a patch to overcome the
limitation or you could try a different backup methodology.
Steven
--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.29d #10183 Warp4/FP11.5
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 06 |
October |
2001 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.