You have a failover cluster that has a Cluster Shared Volume (CSV) configured.
You have to extend the CSV volume.
From a non-coordinator node, you use the Diskpart command or a Windows PowerShell cmdlet to extend the volume.
In this scenario, the extend process is completed successfully. However, the Capacity section of the Disk Management console continues to show the old disk size value from before the extend process. In the Cluster GUI, the disk view shows the correct extended size but the volume size reflects the old values.
Additionally, you cannot reduce the extended volume. If you try to do this, the process fails and you may receive the following error message:
This problem occurs because an extend write operation causes the Cluster Shared Volumes File System (CSVFS) to extend all or some of the following values:
File allocation size
Valid data length
A read operation could cause the CSVFS to query some information from NTFS. On the coordinator node, the CSVFS forwards metadata IO directly to the NTFS volume, whereas other nodes use the Server Message Block (SMB) to forward the metadata over the network.
In the Cluster GUI, you may notice that the Extend Volume option is greyed out on a non-coordinator node.
To resolve this problem, do not run any metadata operation from a non-coordinator node.
For more information about clustering and high-availability, see the following Failover Clustering and Network Load Balancing Team Blog article:
To work around this problem, increase the disk space that’s allocated to the CSV. To do this, extend the disk on the CSV owner node (coordinator node) by using the Cluster GUI, the Diskpart tool, or Windows PowerShell.
Note After you extend the disk, all displayed disk sizes and capacity values are updated to the correct size.
ID articolo: 3189825 - Ultima revisione: 09/21/2016 17:31:00 - Revisione: 3.0
Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2016