Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Storage spaces take a long time to move to another node after a node fails on a Windows Server 2012 R2 failover cluster

Storage spaces take a long time to move to another node after a node fails on a Windows Server 2012 R2 failover cluster

View products that this article applies to.

Symptoms

Consider the following scenario:

  • You have nodes that are running on a Windows Server 2012 R2-based failover cluster.
  • There are many disks in the storage space pool.
  • One of the nodes fails.
In this scenario, the storage spaces take a long time (more than 30 seconds) to move to another node.

↑ Back to the top

Cause

This issue occurs because the persistent reservations cannot be cleared before the storage spaces go online.

↑ Back to the top

Resolution

To resolve this issue, install update rollup 2962409. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2962409  Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2964730
Revision : 1
Created on : 1/7/2017
Published on : 6/10/2014
Exists online : False
Views : 302