Windows 2000 Disk Quotas on Shared Volumes

In Microsoft Windows 2000, disk quotas allow system administrators to track and restrict storage consumption on a per-user basis across shared volumes. Implemented natively through the updated NTFS file system (NTFS 5.0), the operating system monitors file ownership to calculate disk usage, independent of which folder or network share holds the files. This article explains the underlying mechanisms Windows 2000 uses to track, enforce, and manage these disk limits on shared drives.

The Foundation: NTFS File Ownership

Windows 2000 disk quotas operate strictly on the NTFS file system; they cannot be used on FAT or FAT32 partitions. The enforcement mechanism relies entirely on the security identifier (SID) of the file's owner.

  • Tracking by Owner: When a user creates, copies, or takes ownership of a file on an NTFS volume, the entire logical size of that file is charged against that user's quota.
  • Location Independence: Quotas track files across the entire volume. It does not matter whether a user stores files in their personal home directory or a public shared folder on the same volume; all files owned by that user contribute to a single, aggregate usage metric for that specific volume.
  • Compression and Allocation: Windows 2000 measures uncompressed logical file sizes rather than the actual physical clusters consumed on the disk, ensuring consistent tracking regardless of whether NTFS compression is enabled.

Volume-Level Scope

Disk quotas are configured and enforced per volume, not per share or per folder. If a single physical disk contains drive D: with three separate shared folders (\\Server\Share1, \\Server\Share2, and \\Server\Share3), a user assigned a 100 MB quota on D: has a combined limit of 100 MB across all three shares combined. Quotas cannot be applied to individual network shares directly unless each share resides on its own dedicated NTFS volume.

Warning Levels and Hard Limits

Administrators configure quota policies with two distinct thresholds:

  1. Quota Warning Level (Soft Limit): A threshold that triggers a warning. When a user reaches this amount of storage, the system can write an event to the Windows System Event Log if logging is enabled. The user is not blocked from writing additional data.
  2. Quota Limit (Hard Limit): The absolute maximum storage capacity granted to the user. When the policy is set to "Deny disk space to users exceeding quota limit," the operating system actively blocks write requests once this ceiling is reached.

The Kernel-Level Enforcement Process

When an application or a network client attempts to write data to a shared NTFS volume, the Windows 2000 kernel handles the enforcement seamlessly:

  1. Quota Table Lookup: NTFS maintains an internal system file named $Quota on the root of each volume. This hidden file indexes usage totals by user SID.
  2. Space Check: During an I/O write request, the NTFS driver inspects the user's SID against the $Quota table to determine current usage relative to the assigned limit.
  3. Denying Write Operations: If the hard limit has been reached and enforcement is enabled, the NTFS driver rejects the I/O request and returns a standard ERROR_DISK_FULL (Out of Disk Space) response to the client application.
  4. Perception of Free Space: When a user with an active quota queries the available capacity of a network share (for example, via Windows Explorer), Windows 2000 calculates the reported "Free Space" based on the user's remaining quota allocation rather than the actual physical free space on the drive.

Administrative Exemptions

Members of the local Administrators group are exempt from disk quota enforcement. While the system still tracks the space consumed by administrators in the $Quota table for auditing purposes, administrative accounts are never blocked from writing data, ensuring that critical maintenance and administrative tasks are not interrupted by quota constraints.