This article was previously published under Q325463
This article has been archived. It is offered "as is" and will no longer be updated.
The Logical Disk counter values for a shared disk on a cluster may continue to appear as zero in System Monitor after a failover and failback occurs for a disk resource. For example, if you start System Monitor on node A in a cluster (in which disk counters are turned on for all disks) and monitor counters for the Logical Disk object and you then fail over a shared disk from node A to node B, the Logical Disk counter values (for example, Logical Disk\Available MBytes) on node A drop to zero. This is the expected behavior. However, if you then fail over the same shared disk back to node A, the Logical Disk counters remain at zero on node A. This is incorrect.
When you fail over the disk resource back to node A, the Logical Disk counters should resume typical operation on node A to correctly reflect the activity on the disk.
Performance counters are being removed when a disk goes offline (such as when the disk fails over to another computer in a cluster). System Monitor has been modified to check the volume status regularly after a volume goes offline, and to reinstate disk counters promptly when the volume comes back online again.
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------- 23-Jul-2002 09:42 5.0.2195.5963 24,848 Perfdisk.dll 21-Jun-2002 10:09 18.104.22.168 3,584 Spmsg.dll 21-Jun-2002 10:10 22.214.171.124 44,544 Spuninst.exe 12-Jun-2001 22:05 5.0.2195.3727 3,856 Svcpack1.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot