The mount point has less than 3 GB of available space
The information in this article applies to:
Visual Studio Team Foundation Server 2010
Windows Server 2003 and Windows Server 2008
The Best Practices Analyzer tool for Team Foundation Server queries a Microsoft Windows Management Instrumentation (WMI) class (Win32_Volume) to determine the value of the FreeSpace key for volume mount points that the computer uses.
A warning appears if the value of the FreeSpace key, when divided by one million and then rounded up to the nearest whole number, is less than 4. This warning indicates that less than 3 gigabytes (GB) of storage space is available for a volume mount point.
You can use volume mount points (also known as NTFS file system junction points) as a location for data storage in a clustered configuration. They are supported when you have Team Foundation Server installed on a computer that is running Windows Server 2003 or Windows Server 2008, Enterprise Edition or Datacenter Edition. By using volume mount points, you can assign more than 26 drive letters and graft or mount a target partition into a folder on another physical disk. Volume mount points are transparent to programs such as Team Foundation Server.
Team Foundation Server can use volumes that are local physical disks, logical volumes, or volume mount points. In any case, the volume should have at least 50 percent free disk space available on all drives. You should ensure a minimum of 25 to 30 percent of free disk space for maintenance, which includes tasks that you perform by using database utilities such as eseutil and isinteg. Also, for maintenance operations such as offline defragmentation, you should have 100 percent more free space than the amount that you are defragmenting. For example, if you are defragmenting a 1 GB database, you should have at least 1 GB of free disk space available.
For security and availability reasons, you should ensure that all disks have plenty of free space. A denial of service attack, a message loop, or a widespread outbreak of a virus can cause excessive consumption of disk space caused by increased message traffic or transaction log activity.
To resolve this issue, reclaim or add disk capacity to the computer.
To resolve a warning about mount point space
Investigate areas to reclaim disk space, and increase available space.
If disk space is very low, consider moving data to another computer that is running Team Foundation Server and that is not space constrained.
For more information about how to use volume mount points in a cluster that is running Windows Server 2003, see article 280297, "How to configure Volume Mount Points on a clustered server" in the Microsoft Knowledge Base.