X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.2 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_LOW,TW_RW,TW_WX
X-Spam-Check-By:	sourceware.org
X-MDAV-Processed:	mail1.multiplay.co.uk, Sat, 08 Jan 2011 02:38:51 +0000
X-Spam-Processed:	mail1.multiplay.co.uk, Sat, 08 Jan 2011 02:38:51 +0000
X-MDRemoteIP:	188.220.16.49
X-Return-Path:	prvs=1989f919f6=killing AT multiplay DOT co DOT uk
X-Envelope-From:	killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To:	cygwin AT cygwin DOT com
Message-ID:	<265F601A437E4A03BE8C665BE7470721@multiplay.co.uk>
From:	"Steven Hartland" <killing AT multiplay DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<3501944D149644D394474781054F5E98 AT multiplay DOT co DOT uk> <4D2783A3 DOT 5000008 AT redhat DOT com> <D43AAA42D53E47AF958054385DAEFB50 AT multiplay DOT co DOT uk> <4D27C896 DOT 30202 AT cygwin DOT com>
Subject:	Re: Strange fstatat / stat behavour on directories causing tar "file changed as we read it" error
Date:	Sat, 8 Jan 2011 02:39:02 -0000
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

----- Original Message ----- 
From: "Larry Hall (Cygwin)"
>> Just NTFS I'm afraid nothing special.
>>
>> You can see the behaviour with ls -l as well, as you would expect.
>>
>> A simpler, which may help is:-
>> ls -l
>> drwxr-xr-x 1 test test 0 Oct 20 14:09 testdir
>> find testdir > /dev/null # lots of files
>> ls -l
>> drwxr-xr-x 1 test test 8192 Oct 20 14:09 testdir
>>
>> uname -a
>> CYGWIN_NT-6.0-WOW64 hern4 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin
>                             ^^^^^
> Did you try with the current version of the cygwin package?  I tried your
> test on W7 uses the 1.7.7 and had no problem.  It would be interesting
> to know if what you're seeing is and old bug or possibly W2K8-specific.

Unfortunately that's not easy as the machines are in production 24/7 and to
upgrade would been to take them offline :(

I'll try to get box installed with 1.7.7 for testing. We've not seen this before
but it does seem to happen quite a lot with this particular directory structure
we have which typically has 90K+ files in 5k+ directories in it, all of which are
small, total size just 400MB

Not 100% sure, but I believe we have had a Windows 7 exhibit the same
behaviour.

Here it takes about 2 - 5mins for what ever is causing the 0 size after a
find to start to happen. Prior to that after the find all dirs show 8192 for size
in an ls.

    Regards
    Steve


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

- Raw text -