[windows2000] Re: System hang copying GB files (2003)
- From: "Sorin Srbu" <sorin.srbu@xxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Tue, 7 Jun 2005 09:44:57 +0200
----Original Message----
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx]On Behalf Of Tim Mangan Sent:
Sunday, June 05, 2005 9:45 PM To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] System hang copying GB files (2003)
> I'm looking at a problem - hoping someone else may have seen it
before..
>
> Windows Server 2003 on a Dell box. When I copy a multi GB file (have
seen
> with 1.5 to 3.5 GB files) from one disk to another on the same server
the
> system semi-hangs. Originally I thought the issue was a new disk I
added,
> but have removed the new disk and found I could reproduce just copying
> between two existing drives. (The files I want to copy are virtual
server
> disks, hence their size. They are normally excluded from backup since
they
> are just temporary test machines so they have never been copied
before. I
> bought the new drive to house these longer term.).
>
> The symptoms are that after about 40 seconds the user interface hangs,
> although copying continues. The box can be pinged, although remote
logon
> attempts get near the logon screen - you get the background but the
"press
> ctrl-alt-del" box never quite makes it up. Running performance
counters
> remotely I continue to get results from counters, although new ones
cannot
> be added because the server isn't responding to the enumeration
request.
> With these counters, however, I see CPU usage drop down at the time of
the
> hang. Memory indications (paged/non-paged, etc..) continue looking
normal
> throughout.
>
> I haven't found anything like this in the Microsoft KB and am running
basic
> hardware tests to see if anything odd shows up there. Sound familiar
to
> anyone?
>
> Timothy Mangan
> Founder, TMurgent Technologies
> tmangan@xxxxxxxxxxxx (+1) 781.492.0403
I've seen this too on my win2k3 servers at home, and have attributed the
"semihangs" to inadequte hardware (the 1ry is a amd classic 700MHz/512MB
ram and the 2ry is an amd tbird 1200Mhz/512MB ram), specifically the
harddrives, as they are ATA-type. I've never seen it on my scsi-servers
at work. I also beleive this is a cache thing too. Nothing to worry
about though, the copy or move-procedure always ends correctly, even if
the server semihangs. I usually see this when handling big files, like
500MB and more.
HTH.
********************************************************
This Weeks Sponsor: Straymonkey.com
Excellent web templates, fonts, and downloads
on this new site brought to you by The Kenzig Group
http://www.straymonkey.com
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
