This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Strange fstatat / stat behavour on directories causing tar "file changed as we read it" error

----- 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

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.


-- Problem reports: FAQ: Documentation: Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]