Windows Server 2000/2003 Thread, Server does not like large files. in Technical; Right, this question has been bugging me for a while.
We've got a 4 year old server that's running 2003 ...
24th September 2010, 11:29 AM #1
Server does not like large files.
Right, this question has been bugging me for a while.
We've got a 4 year old server that's running 2003 and is fitted with 3GB of memory. It has 2 SATA HD's (not RAID) and is networked with a 1Gb link.
From my machine if I copy a large file say 2GB, to one of the server drives, it copies ok but if I copy the same file to the other server drive the progress bar moves very quickly at first then stops with the server HD light lit solid. It will stay like this for a few minutes with the server unresponsive then my machine will report an error and the server will come back to life.
For information the server swap file set at 4977 MB and is on the second drive.
IDG Tech News
24th September 2010, 11:35 AM #2
Probably a dead drive. Check the event log for disk errors.
24th September 2010, 11:55 AM #3
Very obvious stab in the dark, the problem drive is not Fat32 by any chance?
24th September 2010, 12:14 PM #4
The drive is using NTFS and smaller files copy ok. I've tested it with 1GB files and they copy but the server freezes but comes back to life before any errors.
The event log gives these errors at the time I copied the 2GB file.
NTDS (420) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit" at offset 1466368 (0x0000000000166000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
NTDS (420) NTDSA: A request to write to the file "C:\WINDOWS\NTDS\edb.log" at offset 339456 (0x0000000000052e00) for 512 (0x00000200) bytes succeeded, but took an abnormally long time (85 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
24th September 2010, 01:23 PM #5
Robocopy took 17 minutes but it worked.
Originally Posted by jinnantonnix
24th September 2010, 02:58 PM #6
The drive or sata cable are toast or at the very least massivly overloaded. I would be looking at backing up hurridly and looking at the warrenty status along with running the manufacturers drive test tools like seatools (seagate) which can be run from inside windows.
Originally Posted by Jobos
25th September 2010, 03:53 AM #7
What format are the drives in? NTFS or a Fat version, Because Fat doesn't like 4gb and it could be handling it bad.
25th September 2010, 08:53 AM #8
Originally Posted by p858snake
By randle in forum Wireless Networks
Last Post: 24th March 2009, 11:27 PM
By link470 in forum How do you do....it?
Last Post: 28th April 2008, 12:51 PM
By LikesComputers in forum Windows
Last Post: 25th June 2007, 01:33 PM
By Kyle in forum How do you do....it?
Last Post: 25th April 2007, 07:57 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)