Storage Foundation 8.0 Administrator's Guide - Windows
- Overview
- Setup and configuration
- Function overview
- About the client console for Storage Foundation
- Recommendations for caching-enabled disks
- Configure basic disks (Optional)
- About creating dynamic disk groups
- About creating dynamic volumes
- Set desired preferences
- Using the GUI to manage your storage
- Working with disks, partitions, and volumes
- Adding storage
- Disk tasks
- Remove a disk from the computer
- Veritas Disk ID (VDID)
- General Partition/Volume tasks
- Mount a volume at an empty folder (Drive path)
- Expand a dynamic volume
- Shrink a dynamic volume
- Basic disk and volume tasks
- Automatic discovery of SSD devices and manual classification as SSD
- Volume Manager space allocation is SSD aware
- Dealing with disk groups
- Disk groups overview
- Delete a dynamic disk group
- Detaching and attaching dynamic disks
- Importing and deporting dynamic disk groups
- Partitioned shared storage with private dynamic disk group protection
- Fast failover in clustered environments
- iSCSI SAN support
- Settings for monitoring objects
- Event monitoring and notification
- Event notification
- Configuring Automatic volume growth
- Standard features for adding fault tolerance
- Performance tuning
- FlashSnap
- FlashSnap components
- FastResync
- Snapshot commands
- Dynamic Disk Group Split and Join
- Dynamic disk group join
- Using Dynamic Disk Group Split and Join with a cluster on shared storage
- Dynamic Disk Group Split and Join troubleshooting tips
- Fast File Resync
- Volume Shadow Copy Service (VSS)
- Using the VSS snapshot wizards with Microsoft Exchange
- Using the VSS snapshot wizards with Enterprise Vault
- Using the VSS snapshot wizards with Microsoft SQL
- Copy on Write (COW)
- Using the VSS COW snapshot wizards with Microsoft Exchange
- Using the VSS COW snapshot wizards with Microsoft SQL
- Configuring data caching with SmartIO
- Typical deployment scenarios
- About cache area
- Configuring SmartIO
- Frequently asked questions about SmartIO
- Dynamic Multi-Pathing
- Configuring Cluster Volume Manager (CVM)
- Configuring a CVM cluster
- Administering CVM
- Access modes for cluster-shared volumes
- Storage disconnectivity and CVM disk detach policy
- Unconfiguring a CVM cluster
- Command shipping
- About I/O Fencing
- Administering site-aware allocation for campus clusters
- SFW for Hyper-V virtual machines
- Introduction to Storage Foundation solutions for Hyper-V environments
- Live migration support for SFW dynamic disk group
- Preparing the host machines
- Configuring the SFW storage
- Administering storage migration for SFW and Hyper-V virtual machine volumes
- Optional Storage Foundation features for Hyper-V environments
- Microsoft Failover Clustering support
- Configuring a quorum in a Microsoft Failover Cluster
- Implementing disaster recovery with Volume Replicator
- Troubleshooting and recovery
- Using disk and volume status information
- Resolving common problem situations
- Commands or procedures used in troubleshooting and recovery
- Rescan command
- Repair volume command for dynamic mirrored volumes
- Additional troubleshooting issues
- Disk issues
- Volume issues
- Disk group issues
- Connection issues
- Issues related to boot or restart
- Cluster issues
- Dynamic Multi-Pathing issues
- vxsnap issues
- Other issues
- CVM issues
- Appendix A. Command line interface
- Overview of the command line interface
- vxclustadm
- vxvol
- vxdg
- vxclus
- vxdisk
- vxassist
- vxassist (Windows-specific)
- vxsd
- vxedit
- vxdmpadm
- vxcbr
- vxsnap
- vxscrub
- sfcache
- Tuning SFW
- Appendix B. VDID details for arrays
Safeguarding the expand volume operation in SFW against limitations of NTFS
To prevent users from expanding volumes beyond the limitations of NTFS for NTFS cluster size, the following safeguard is implemented:
SFW does a check for the NTFS cluster size of the volume while expanding it.
The operation fails, if the user tries to expand the volume beyond a limit.
The limit depends upon the cluster size of the specified volume during its creation.
When SFW receives an expand volume request, it validates the requested new size against the MAX SIZE supported for that volume.
If the size exceeds the limit, the expand operation results in a failure, displaying the following error message:
The extend operation did not complete because the cluster count is higher than expected.
Architecturally NTFS supports: 2^32 clusters minus one cluster count.
The General formula is:
((2^32)-1) * (user-selected size in bytes of a single cluster before format)
= maximum FS size for that instance possible during grow/extend without reformat.
So we have ((2^32) -1 = (4,294,967,296) -1 = 4,294,967,295 clusters count.
Therefore, for a cluster size of 512 bytes, maximum size of the mountable file system:
(2^32)-1) cluster count X 512 bytes represented by each cluster = 2199023255040 bytes.
Hence, for a 512 Bytes cluster sized volume, (2199023255040 bytes) 2 TB is the supported file system size.
The following table is used to check limitations against the cluster size:
Table: Limitation against the cluster size
Cluster Size | Maximum NTFS Volume Size |
---|---|
512 | 2,199,023,255,040 (2TB) |
1,024 | 4,398,046,510,080 (4TB) |
2,048 | 8,796,093,020,160 (8TB) |
4,096 | 17,592,186,040,320 (16TB) |
8,192 | 35,184,372,080,640 (32TB) |
16,384 | 70,368,744,161,280 (64TB) |
32,768 | 140,737,488,322,560 (128TB) |
65,536 | 281,474,976,645,120 (256TB) |