I know your'e probably all bored by now but it's useful for me to record what happened somewhere so I can remember!
So I decided to reboot, can't remember why, and it took ages to come back and when it did it was in the bad state. I as able to start the batch file as it's on a local disk to write files to the NAS. It just writes a file which is called whatever the hhmmss is then pauses for 15 secs before doing it again. It's at the bottom of this post.
So in the network folder I have a period of about 35 minutes (from 11:30:01 till it freed itself up again at 12:02) when I should have had about 140 files. I actually had 8 files. The program echoes what it is doing on the screen, so you can see if sitting for ages in the copy command, then suddenly executing it and the subsequent commends in the loop (recapturing and formatting the time) then sticking in the copy again. So it is not stopped, it is just extraordinarily slow for about 32 minutes.
The performance monitor shows nothing untoward during this time (though I have stopped a couple of things starting at startup as they burst into action occasionally and I never need that). I have some screen captures of the performance monitor after it rectified itself and if you take it that a queue of tasks is suddenly released again I can't see anything untoward.
I also set another copy going to write to the local disk which ran absolutely fine without missing a beat (or a file).
I've poked about in various logs and found one of two things of interest, and one led me to this report on the internet tinyurl.com/y6nj8ae8 so, although they seem to be set to overwrite, I cleared down the logs (after copying them).
I could (I did!!) go on and on but that's enough for now!
Here's the batch file:
set bfolder=wcopy
:START
SET HOUR=%TIME:~0,2%
IF "%HOUR:~0,1%" == " " SET HOUR=0%HOUR:~1,1%
set m=%TIME:~3,2%
set s=%TIME:~6,2%
copy d:g.bat w:%bfolder%%hour%%m%%s%
TIMEOUT 15
goto START
and it works a treat
|
PC hanging new
PC hanging new
