SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 06 | October | 2001 ]

<< Previous Message << >> Next Message >>


Date: Sat, 6 Oct 2001 09:42:30 PDT
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: zip still won't zip

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <3BBF2A35.3F17@peterskye.com>, on 10/06/01
at 08:59 AM, Peter Skye 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.