Storage Foundation 7.3 Administrator's Guide - Linux
- Section I. Introducing Storage Foundation
- Overview of Storage Foundation
- How Dynamic Multi-Pathing works
- How Veritas Volume Manager works
- How Veritas Volume Manager works with the operating system
- How Veritas Volume Manager handles storage management
- Volume layouts in Veritas Volume Manager
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- How VxVM handles hardware clones or snapshots
- Volume encryption
- How Veritas File System works
- Section II. Provisioning storage
- Provisioning new storage
- Advanced allocation methods for configuring storage
- Customizing allocation behavior
- Using rules to make volume allocation more efficient
- Understanding persistent attributes
- Customizing disk classes for allocation
- Specifying allocation constraints for vxassist operations with the use clause and the require clause
- Creating volumes of a specific layout
- Customizing allocation behavior
- Creating and mounting VxFS file systems
- Creating a VxFS file system
- Mounting a VxFS file system
- tmplog mount option
- ioerror mount option
- largefiles and nolargefiles mount options
- Resizing a file system
- Monitoring free space
- Extent attributes
- Section III. Administering multi-pathing with DMP
- Administering Dynamic Multi-Pathing
- Discovering and configuring newly added disk devices
- About discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Administering DMP using the vxdmpadm utility
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Discovering and configuring newly added disk devices
- Dynamic Reconfiguration of devices
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Managing devices
- Displaying disk information
- Changing the disk device naming scheme
- Adding and removing disks
- Event monitoring
- Administering Dynamic Multi-Pathing
- Section IV. Administering Storage Foundation
- Administering sites and remote mirrors
- About sites and remote mirrors
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Failure and recovery scenarios
- Administering sites and remote mirrors
- Section V. Optimizing I/O performance
- Veritas File System I/O
- Veritas Volume Manager I/O
- Managing application I/O workloads using maximum IOPS settings
- Section VI. Using Point-in-time copies
- Understanding point-in-time copy methods
- When to use point-in-time copies
- About Storage Foundation point-in-time copy technologies
- Volume-level snapshots
- Storage Checkpoints
- About FileSnaps
- About snapshot file systems
- Administering volume snapshots
- Traditional third-mirror break-off snapshots
- Full-sized instant snapshots
- Creating instant snapshots
- Adding an instant snap DCO and DCO volume
- Controlling instant snapshot synchronization
- Creating instant snapshots
- Cascaded snapshots
- Adding a version 0 DCO and DCO volume
- Administering Storage Checkpoints
- Storage Checkpoint administration
- Administering FileSnaps
- Administering snapshot file systems
- Understanding point-in-time copy methods
- Section VII. Optimizing storage with Storage Foundation
- Understanding storage optimization solutions in Storage Foundation
- Migrating data from thick storage to thin storage
- Maintaining Thin Storage with Thin Reclamation
- Reclamation of storage on thin reclamation arrays
- Identifying thin and thin reclamation LUNs
- Veritas InfoScale 4k sector device support solution
- Section VIII. Maximizing storage utilization
- Understanding storage tiering with SmartTier
- Creating and administering volume sets
- Multi-volume file systems
- Features implemented using multi-volume file system (MVFS) support
- Adding a volume to and removing a volume from a multi-volume file system
- Volume encapsulation
- Load balancing
- Administering SmartTier
- About SmartTier
- Placement classes
- Administering placement policies
- File placement policy rules
- Multiple criteria in file placement policy rule statements
- Using SmartTier with solid state disks
- Sub-file relocation
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Deduplicating data
- Compressing files
- About compressing files
- Use cases for compressing files
- Migrating files to the cloud using Simple Storage Service (S3) Connector
- Section IX. Administering storage
- Managing volumes and disk groups
- Rules for determining the default disk group
- Moving volumes or disks
- Monitoring and controlling tasks
- Performing online relayout
- Adding a mirror to a volume
- Managing disk groups
- Disk group versions
- Displaying disk group information
- Importing a disk group
- Moving disk groups between systems
- Importing a disk group containing hardware cloned disks
- Handling conflicting configuration copies
- Destroying a disk group
- Backing up and restoring disk group configuration data
- Managing plexes and subdisks
- Technology Preview: Erasure coding in Veritas InfoScale storage environments
- Decommissioning storage
- Rootability
- Encapsulating a disk
- Rootability
- Sample supported root disk layouts for encapsulation
- Encapsulating and mirroring the root disk
- Administering an encapsulated boot disk
- Quotas
- Using Veritas File System quotas
- File Change Log
- Managing volumes and disk groups
- Section X. Reference
- Appendix A. Reverse path name lookup
- Appendix B. Tunable parameters
- Tuning the VxFS file system
- Methods to change Dynamic Multi-Pathing tunable parameters
- Tunable parameters for VxVM
- Methods to change Veritas Volume Manager tunable parameters
- Appendix C. Command reference
Creating erasure coded volumes on a single node with DAS or SAN storage
The procedure assumes that the disk array exports 8 LUNs of 2 TB each with disks d1, d2, ... d8.
To create erasure coded volumes on a single node with DAS or SAN storage
- Create a disk group, if the required set of disks are not already part of some disk group.
# vxdg init dg1 d1 d2 ... d8
- Create an erasure coded volume, namely testvol, striped across 5 data disks with fault-tolerance of 3 in the disk group:
# vxassist -g dg1 make vol1 1024g \ layout=ecoded ncol=5 nparity=3
If you want specific disks in the disk group to be used for the volume, you can specify the disks as follows:
# vxassist -g dg1 make vol1 1024g \ layout=ecoded ncol=5 nparity=3 d1 d2 ... d8
The following sample configuration uses a disk group
dg1
containing 10 disks, each of size 256 GB:# vxprint Disk group: dg1 TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg dg1 dg1 - - - - - - dm huawei-s2600t0_0 huawei-s2600t0_0 - 534685488 - - - - dm huawei-s2600t0_1 huawei-s2600t0_1 - 534685488 - - - - dm huawei-s2600t0_2 huawei-s2600t0_2 - 534685488 - - - - dm huawei-s2600t0_3 huawei-s2600t0_3 - 534685488 - - - - dm huawei-s2600t0_4 huawei-s2600t0_4 - 572437536 - - - - dm huawei-s2600t0_5 huawei-s2600t0_5 - 582921600 - - - - dm huawei-s2600t0_6 huawei-s2600t0_6 - 582921600 - - - - dm huawei-s2600t0_7 huawei-s2600t0_7 - 582921600 - - - - dm huawei-s2600t0_8 huawei-s2600t0_8 - 582921600 - - - - dm huawei-s2600t0_9 huawei-s2600t0_9 - 582921600 - - - -
If you want to create a 1 GB erasure coded volume
vol1
, which is tolerant to 3 disk failures and has data striped across 5 disks, run the following command:# vxassist -g dg1 make vol1 1g \ layout=ecoded nparity=3 ncols=5
To view the volume configuration:
# vxprint . . v vol1 fsgen ENABLED 2097280 - ACTIVE - - pl vol1-01 vol1 ENABLED 2097280 - ACTIVE - - sd subdisk_0-01 vol1-01 ENABLED 419456 0 - - - sd subdisk_1-01 vol1-01 ENABLED 419456 0 - - - sd subdisk_2-01 vol1-01 ENABLED 419456 0 - - - sd subdisk_3-01 vol1-01 ENABLED 419456 0 - - - sd subdisk_4-01 vol1-01 ENABLED 419456 0 - - - sd subdisk_5-01 vol1-01 ENABLED 419456 0 PARITY - - sd subdisk_6-01 vol1-01 ENABLED 419456 0 PARITY - - sd subdisk_7-01 vol1-01 ENABLED 419456 0 PARITY - -
In the output, note that the plex has 8 subdisks associated with it (each represent a column), each created on a different disk. You may also have multiple subdisks concatenated to represent one column just as with stripe-volume layout (RAID-0). The subdisks with state marked "PARITY" contain the encoded data. The layout attribute of the erasure coded volume is "ECODED".
You can verify the layout of the volume by running the following command:
# vxprint -g dg1 -F% layout vol1 ECODED