This is the mail archive of the
mailing list for the Cygwin project.
Re: Strange fstatat / stat behavour on directories causing tar "file changed as we read it" error
On Jan 9 00:22, Cyrille Lefevre wrote:
> Le 08/01/2011 04:13, Larry Hall (Cygwin) a Ãcrit :
> > On 1/7/2011 9:39 PM, Steven Hartland wrote:
> > <snip>
> >> 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.
> IMHO, the first time the directory size is read, the size used by
> FindFirstFile/FindNextFile (or something like that :-) is zero'ed,
> then the directory size is updated while the directory is traversed.
> also the directory size doesn't seem to shrink on entry removal,
> even after a reboot.
I can not reproduce the effect, at least not on W7, but apparently it
happens on some systems. So, given that the directory size is
irrelevant for all practical purposes anyway, and given that there's no
application which has problems with a directory size of 0, should Cygwin
just always set st_size to 0 for directories? Independent of the
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple