Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Subject: Re: 20040217 unhoses unzip!
From: Thomas L Roche <tlroche AT us DOT ibm DOT com>
Message-ID: <OFD41AC46C.88C0A279-ON85256E3E.0019009F-85256E3E.001A3556@us.ibm.com>
Date: Tue, 17 Feb 2004 23:46:15 -0500
Content-Type: text/plain; charset="US-ASCII"

On Tue, 17 Feb 2004, Christopher Faylor wrote:
>> Hmm.  I really don't understand why unless you were unzipping *a lot*
>> of files with long filenames.  There should have been something like
>> 32MB of space to waste before you saw the problem.

Igor Pechtchanski Tue, 17 Feb 2004 22:09:51 -0500 (EST) 
> They were.  1.4G zip archives with tens of thousands of small files, 
many
> with path lengths > 1k.

That also explains why the problem only appeared well into a run (30-60
min), and why it was unreproducible "in the small" (i.e. a testibly-bad
but sendably-short input). Even our relatively small (~100 MB) base files
unzip'ed OK throughout.

Hoping this helps emacs, too ... can't see how, other than it's also hot
for RAM, but one can hope :-)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/