X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 08 Jan 2011 05:18:46 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 08 Jan 2011 05:18:45 +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: <6AE2683F3A6748B9BE62EDDE918D7668@multiplay.co.uk> From: "Steven Hartland" To: References: <3501944D149644D394474781054F5E98 AT multiplay DOT co DOT uk> <4D2783A3 DOT 5000008 AT redhat DOT com> <4D27C896 DOT 30202 AT cygwin DOT com> <265F601A437E4A03BE8C665BE7470721 AT multiplay DOT co DOT uk> <4D27D66F DOT 8030201 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 05:18:58 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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)" >> 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. > > Ah, that's interesting. I see no such time-lag here. Just to be 100% clear the pattern I see is:- 1. ls -l gives some dirs in testdir as 0 size 2. Run: find testdir 3. ls -l reports all dirs in testdir as 8192 size 4. wait 30 seconds 5. ls -l reports all dirs in testdir as 8192 size 6. wait another minute or so 7. ls -l reports some dirs in testdir as 8192 size and some as 0 > But of course I'm working in an empty directory. I'm also going to guess > that you're mounting your directory with the 'noacl' option. If that's true, > you might try removing that option to see if it makes any difference. From what I've seen it needs subdirs / files to cause the strangeness. Don't think we are using noacl at least mount doesn't show it:- C:/testdir on /usr/local/testdir type ntfs (binary) /etc/fstab shows:- c:/testdir /usr/local/testdir ntfs binary,auto 0 0 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