Large Windows 2003 File System

Microsoft Windows Server 2003
I have a two part question. I have a large file system with 65 million files and 2TB of disk space on a Windows 2003 R2 server. The file system locks up randomly and struggles with counting the number of files. Does anyone run similar sized file systems and run into similar problems? Are there limits in Windows 2003 32bit OS. The second part is growing the volumes beyond 2TB. It seems Win2k3 recommends spanning which we don't like. How do others deal with volumes that need to be larger than 2TB. Note: for application reasons I can only have one volume.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Yes we have a file server with a very large number of files. It’s to be expected that the system will lock up when counting the files. When dealing with these large numbers of files it’s best to manage the system as much as possible from the command line.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • EastCoastGuy
    The command line seems to lock up as well. We use diruse and the system runs out of resources before completing a full count. I have 82 million files. Does Windows 2003 run into limits with this many files? Any suggestions on tunning. I have disabled short file names and last access file attributes.
    250 pointsBadges:
  • Denny Cherry
    As far as I know it doesn't run into any limits on the number of files. However we don't ever count the number of files. The server in our enviroment is accessed via a web page and the file paths are system generated based on data from the database.
    69,065 pointsBadges:
  • Jerry Lees
    I have personally seen two instances where the number of files caused extreme slowness of a server. One had around 500,000 to 750,000 PDF files in a folder structure for a web gift certificate application. This simply amounted to programmers not cleaning up after themselves since the files were useless. The other had more files in one folder for the same reason. To tell you how bad it made the server preform... any one remember the "freaking donuts" youtube videos in July around the launch of a major movie sponsored by a freaky big headed guy??? ;-) It doesn't make the system lock up... it will recover, but windows had a real problem with that many files in one folder structure. MrDenny is right about the Comand line management of the files. If a folder gets that far out of control, then you need to manage it from the comandline becasue windows tried to enumerate the files before displaying them in explorer.
    5,335 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: