delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,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 01:59:49 +0000 |
X-Spam-Processed: | mail1.multiplay.co.uk, Sat, 08 Jan 2011 01:59:49 +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: | <D43AAA42D53E47AF958054385DAEFB50@multiplay.co.uk> |
From: | "Steven Hartland" <killing AT multiplay DOT co DOT uk> |
To: | "Eric Blake" <eblake AT redhat DOT com>, <cygwin AT cygwin DOT com> |
References: | <3501944D149644D394474781054F5E98 AT multiplay DOT co DOT uk> <4D2783A3 DOT 5000008 AT redhat 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:00:00 -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: "Eric Blake" On 01/07/2011 11:21 AM, Steven Hartland wrote: > What file system is this on? Someone else reported the same behavior > for "Samba share on QNX through Virtual PC." - if the problem is limited > to just a subset of (known-buggy) file systems, it would be nicer to > limit the workaround to just those file systems (and have st_size always > return 0 for directories from those systems). FS was just NTFS, at first we thought it might be being caused by compression being enabled on the files / directories but we confirmed the behavour on an machine with uncompressed volumes as well. >> Is there some "meta data" caching going on in cygwin or >> Windows which causes this very strange behaviour? > Giving us more details about your filesystem would help us answer that > question. 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 Running under Web Server 2008 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |