- administration
- failover and RAID units
- RAID Units and XVM Failover V2
- RAID units and XVM failover
- RAID Units and XVM Failover V2
- affinity
- Controller Configuration
- affinity keyword and ALUA RAID
- Do Not Use affinity or preferred
Keywords for ALUA RAID
- affinity=0
- Set Appropriate affinity
Values for Non-ALUA LUNs
- affinity=none
- Show the Available Unlabeled Paths
- ALUA
- Path Failover
- Controller Configuration
- Show the Available Unlabeled Paths
- attach command
- Reorganizing Volumes
- attach
- blue text in the GUI
- Help Menu
- caveats
- XVM Best Practices
- change command
- Gathering Statistics for Physical Disks and Logical Resources
- Modifying Volume Elements with the change Command
- change
- stat option
- Overview of XVM Statistics
- child syntax
- Specifying Objects by Piece Number
- child volume element
- definition
- Children
- clean
- state
- Displaying the State of Volume Elements and Physvols
- clear
- option of mirror command
- Mirror Revive at Creation
- cluster domain
- Support for a Cluster Environment
- CXFS Service Requirements for Cluster Domain
- Interactive Use
- Changing the Current Domain with the
set Command
- cluster environment
- Support for a Cluster Environment
- cluster system startup
- Cluster System Startup
- collapse command
- Making Online Changes
- collapse
- colors and states
- Key to Icons and States
- command buttons
- Shortcuts Using Command Buttons
- concat
- creation
- Creating Concats
- definition
- Concat
- statistics
- Concat Statistics
- concat command
- Creating Concats
- concat
- configuration tools
- Use XVM Configuration Tools Appropriately
- considerations
- XVM Best Practices
- contacting SGI with problems
- Reporting Problems to SGI
- controller configuration
- Controller Configuration
- crash
- Using the System Dump Analysis Tool
- custom_persistent_name_scan.sh
- Path Manager
- CXFS
- Overview of Domains
- CXFS and XVM
- Support for a Cluster Environment
- CXFS GUI
- XVM Manager and CXFS Manager
- data subvolume
- definition
- Subvolume
- delete command
- Deleting Volume Elements
- Deleting Volume Elements
- Deleting Volume Elements with the
delete Command
- delete -nonslice
- Restripe Efficiently
- detach command
- Detaching Volume Elements
- Reorganizing Volumes
- detach
- details area
- GUI Window Layout
- device hot plug
- Device Hot Plug
- disabled state
- Displaying the State of Volume Elements and Physvols
- disk configuration
- Configuring Disks
- disk paths
- Purpose of XVM Failover
- domain
- cluster
- Overview of Domains
- CXFS Service Requirements for Cluster Domain
- Changing the Current Domain with the
set Command
- local
- Overview of Domains
- Overview of Domains
- Changing the Current Domain with the
set Command
- domains
- Support for a Cluster Environment
- drag-and-drop
- Using Drag-and-Drop
- Configuring Disks
- dump analysis
- Using the System Dump Analysis Tool
- dump command
- Replacing a Physvol
- Saving and Regenerating an XVM Configuration
- Regenerating Physvols using the dump Command
- Reconstructing Volume Elements with the
dump Command
- Edit menu
- Edit Menu
- /etc/failover2.conf
- Controller Configuration
- /etc/fstab
- Do Not Run fsck on Filesystems that Use XVM
Devices
- /etc/modprobe.d/sgi-cxfs-xvm.conf
- Making Permanent Parameter Changes
- /etc/xvm/custom_persistent_name_scan.sh
- Path Manager
- /etc/xvm/pm_bypass_single_path.sh
- Path Manager
- /etc/xvm/xvm_persistent_name_scan.sh
- Path Manager
- examples
- GUI screens
- GUI Window Layout
- external log subvolume
- Subvolume
- failover
- See path failover
- features
- XVM Features
- File menu
- Making Changes Safely
- File Menu
- Find text field
- Selecting Items to View or Modify
- foconfig command
- Pushing the Contents of the /etc/failover2.conf
File to the Kernel
- -force option
- delete command
- Deleting Volume Elements
- detach
- Detaching Volume Elements
- unlabel command
- Destroying Physvols
- foreign disk
- XVM Objects
- Overview of Domains
- Specifying Objects by Name
- Foreign Disks
- foswitch command
- Setting All LUNs to the Preferred Path
- Returning to Preferred Path
- fsck
- XVM Best Practices
- GPT label
- Making a GPT Label
- growing volumes
- Growing the Volume
- GUI
- See XVM GUI
- multiple instances
- Making Changes Safely
- starting
- Logging In
- web-based version
- Starting the GUI from the Web
- GUI and xvm command differences
- Important GUI and xvm Command Differences
- GUI help
- Getting More Information
- GUI invocation
- Starting the GUI via the Command Line
- guided configuration tasks
- GUI Features
- hard-disk drive
- XVM Configuration for Mixing SSD and HDD Media
- HBA configuration
- HBA Configuration
- HBA usage
- Select HBA Usage for Each LUN
- HDD
- XVM Configuration for Mixing SSD and HDD Media
- help command
- Online Help for xvm CLI Commands
- Online Help for xvm CLI Commands
- Help menu
- Help Menu
- hot plug
- Device Hot Plug
- ibound
- XVM Configuration for Mixing SSD and HDD Media
- icons and states
- Key to Icons and States
- inaccessible disks
- Removing Configuration Information for Inaccessible Disks
- incomplete state
- Displaying the State of Volume Elements and Physvols
- inconsistent state
- Displaying the State of Volume Elements and Physvols
- input instructions
- Getting More Information
- insert command
- Making Online Changes
- insert
- inserting elements
- Insertion and Removal
- installation
- Installing XVM
- item view
- See details view
- keywords
- xvm command
- Command Abbreviation
- Knowledgebase
- Using SGI Knowledgebase
- label command
- Creating Physvols
- Assigning Disks to XVM with the label
Command
- Label the Paths
- Striping a Portion of a Disk
- layering volumes
- Flexible Volume Layering and Configuration
- limitations
- XVM Best Practices
- Linux
- configuring XVM volumes
- Preparing to Configure XVM Volumes in the Local
Domain
- device directories
- Device Directories and Pathnames
- load balancing
- Path Manager
- local domain
- Support for a Cluster Environment
- Overview of Domains
- Changing the Current Domain with the
set Command
- log subvolume
- definition
- Subvolume
- logical volume
- XVM Features
- See volume
- Making a GPT label
- Making a GPT Label
- management tools
- Management Tools
- manually changing physvol paths
- Manually Changing Physvol Paths
- mediaerr state
- Displaying the State of Volume Elements and Physvols
- mirror
- attaching
- Attaching Volume Elements
- creation
- Creating Mirrors
- definition
- Mirror
- detach
- Detaching Volume Elements
- detach
- mirroring stripes
- Mirroring Individual Stripe Members
- no synchronize at creation
- Mirror Revive at Creation
- primary leg
- Primary Leg
- read policies
- Read Policies
- removal
- Removing a Mirror
- revive
- Attaching Volume Elements
- Creating Mirrors
- mirror
- detach
- Mirror Revives
- Mirror Revives on Recovery in a Cluster
- statistics
- Mirror Statistics
- mirror command
- Creating Mirrors
- mirror
- -clean option
- Mirror Revive at Creation
- -norevive option
- Mirror Revive at Reboot
- mirror performance options
- Mirror Performance Options
- missing XVM volumes
- Important GUI and xvm Command Differences
- multiple address spaces
- Multiple Address Spaces
- multiple-path selection
- HBA Configuration
- -name option
- Assigning Disks to XVM with the label
Command
- naming
- volume elements
- Naming Volume Elements
- volumes
- Automatic Creation of a Volume and Subvolume
- non-ALUA RAID
- Path Failover
- Controller Configuration
- Set Appropriate affinity
Values for Non-ALUA LUNs
- Set the preferred Path for Each Non-ALUA LUN
- norevive
- option of mirror command
- Mirror Revive at Reboot
- NUMA interconnect traffic
- Path Manager
- NUMAlink
- HBA Configuration Differences for SGI UV Systems
- object names
- regular expressions
- Regular Expressions
- object type
- Specifying Objects by Name
- offline state
- Displaying the State of Volume Elements and Physvols
- Disabling Volume Elements
- volume
- Deleting Volume Elements
- online configuration changes
- Online Configuration Changes
- online state
- Displaying the State of Volume Elements and Physvols
- Disabling Volume Elements
- open state
- Displaying the State of Volume Elements and Physvols
- operation
- XVM Operation
- output to gather
- Reporting Problems to SGI
- path failover
- Path Failover
- affinity
- Controller Configuration
- Setting a New Affinity
- affinity=0
- Set Appropriate affinity
Values for Non-ALUA LUNs
- affinity=none
- Show the Available Unlabeled Paths
- ALUA
- Controller Configuration
- Show the Available Unlabeled Paths
- controller configuration
- Controller Configuration
- /etc/failover2.conf
- Show the Available Unlabeled Paths
- label the paths
- Label the Paths
- manually changing physvol paths
- Manually Changing Physvol Paths
- new device
- Switching to a New Device
- non-ALUA RAID
- Controller Configuration
- Set Appropriate affinity
Values for Non-ALUA LUNs
- Set the preferred Path for Each Non-ALUA LUN
- preferred
- Controller Configuration
- priority
- Controller Configuration
- HBA Configuration Differences for SGI UV Systems
- purpose
- Purpose of XVM Failover
- pushing to the kernel
- Pushing the Contents of the /etc/failover2.conf
File to the Kernel
- RAID units
- RAID Units and XVM Failover V2
- RM610/660
- TP9100 and RM610/660
- S330
- TP9300, TP9500, TP9700, and S330
- select HBA usage
- Select HBA Usage for Each LUN
- set all LUNs to the preferred path
- Setting All LUNs to the Preferred Path
- SGI UV systems
- HBA Configuration Differences for SGI UV Systems
- SGIAVT
- TP9100 and RM610/660
- TP9300, TP9500, TP9700, and S330
- SGIAVT mode
- Controller Configuration
- show the available unlabeled paths
- Show the Available Unlabeled Paths
- TP9100
- TP9100 and RM610/660
- TP9300, TP9500, TP9700
- TP9300, TP9500, TP9700, and S330
- working set
- Set Appropriate affinity
Values for Non-ALUA LUNs
- path manager
- Path Manager
- path specification
- Specifying Objects by Name
- pathmgr kernel module
- Path Manager
- perform tasks
- Performing Tasks
- Performance Co-Pilot
- Built-in Statistics Support
- physical volume
- See physvol
- physical volume See physvol
- XVM Objects
- physvol
- adding to a running system
- Adding a Physvol to Running System
- creation
- Creating Physvols
- definition
- XVM Objects
- destruction
- Destroying Physvols
- display
- Displaying Physvols
- management
- Managing Physvols
- replacing
- Replacing a Physvol
- statistics
- Physvol Statistics
- physvol object type
- definition
- Specifying Objects by Name
- pathname
- Specifying Objects by Name
- piece
- definition
- Children
- piece syntax
- Specifying Objects by Piece Number
- pieceoffline state
- Displaying the State of Volume Elements and Physvols
- pm_ display_io_activity
- pm_display_io_activity
- pm_bypass_single_path.sh
- Path Manager
- pm_small_io_size_limit
- pm_small_io_size_limit
- preferred keyword and ALUA RAID
- Do Not Use affinity or preferred
Keywords for ALUA RAID
- preferred keyword in /etc/failover2.conf
- Controller Configuration
- primary leg, mirror
- Primary Leg
- priority keyword in /etc/failover2.conf
- HBA Configuration
- HBA Configuration Differences for SGI UV Systems
- Privilege Manager
- Logging In
- probe command
- Probing a Physical Volume with the probe Command
- Label the Paths
- probing a disk. See probe command
- Adding a Physvol to Running System
- problem reporting
- Reporting Problems to SGI
- pushing failover2.conf to the kernel
- Pushing the Contents of the /etc/failover2.conf
File to the Kernel
- RAID units and path failover
- RAID Units and XVM Failover V2
- RAID Units and XVM Failover V2
- real-time subvolume
- definition
- Subvolume
- regular expressions
- Regular Expressions
- remake command
- Reorganizing Volumes
- remake
- removing elements
- Insertion and Removal
- reporting problems
- Reporting Problems to SGI
- reprobe
- Removing Configuration Information for Inaccessible Disks
- reprobe command
- Removing Configuration Information with the
reprobe Command
- Label the Paths
- restripe
- Restripe Efficiently
- reviving state
- Displaying the State of Volume Elements and Physvols
- RM610/660 and path failover
- TP9100 and RM610/660
- root privileges
- root Requirement
- round-robin mirror read policy
- Read Policies
- rt subvolume
- Subvolume
- S330 and path failover
- TP9300, TP9500, TP9700, and S330
- safe commands
- Safe Versus Unsafe Commands
- -safe option
- detach
- Detaching Volume Elements
- general
- Attaching Volume Elements
- Safe Versus Unsafe Commands
- selecting items to view or modify
- Selecting Items to View or Modify
- self-identifying volumes
- Self-Identifying Volumes
- sequential mirror read policy
- Read Policies
- set command
- Changing the Current Domain with the
set Command
- SGI Knowledgebase
- Using SGI Knowledgebase
- SGI UV systems
- HBA Configuration Differences for SGI UV Systems
- SGIAVT
- TP9100 and RM610/660
- TP9300, TP9500, TP9700, and S330
- SGIAVT mode
- Controller Configuration
- TP9300, TP9500, TP9700, and S330
- shortcuts
- Shortcuts Using Command Buttons
- show command
- Displaying the State of Volume Elements and Physvols
- Displaying Physical Volumes with the
show Command
- Displaying Volume Elements with the
show Command
- Striping a Portion of a Disk
- slice
- creation
- Creating Slices
- definition
- Slice
- statistics
- Slice Statistics
- slice command
- Creating Slices
- slice
- Striping a Portion of a Disk
- slices
- Large Number of Slices
- solid-state drive
- XVM Configuration for Mixing SSD and HDD Media
- SSD
- XVM Configuration for Mixing SSD and HDD Media
- state
- clean
- Displaying the State of Volume Elements and Physvols
- disabled
- Displaying the State of Volume Elements and Physvols
- incomplete
- Displaying the State of Volume Elements and Physvols
- inconsistent
- Displaying the State of Volume Elements and Physvols
- mediaerr
- Displaying the State of Volume Elements and Physvols
- offline
- Displaying the State of Volume Elements and Physvols
- online
- Displaying the State of Volume Elements and Physvols
- open
- Displaying the State of Volume Elements and Physvols
- pieceoffline
- Displaying the State of Volume Elements and Physvols
- reviving
- Displaying the State of Volume Elements and Physvols
- tempname
- Displaying the State of Volume Elements and Physvols
- valid
- Displaying the State of Volume Elements and Physvols
- volume element
- Displaying the State of Volume Elements and Physvols
- state in the GUI
- Displaying State
- statistics
- Built-in Statistics Support
- Gathering Statistics for Physical Disks and Logical Resources
- Overview of XVM Statistics
- concat
- Concat Statistics
- mirror
- Mirror Statistics
- physvol
- Physvol Statistics
- slice
- Slice Statistics
- stripe
- Stripe Statistics
- subvolume
- Subvolume Statistics
- steal command
- Foreign Disks
- storage types
- Multiple Storage Types
- stripe
- creation
- Creating Stripes
- definition
- Stripe
- size
- stripe
- statistics
- Stripe Statistics
- unit
- stripe
- stripe command
- Creating Stripes
- stripe
- Striping a Portion of a Disk
- subvolume
- creation
- Creating Subvolumes
- data
- Subvolume
- definition
- Subvolume
- limitations
- Subvolume
- log
- Subvolume
- names
- Specifying Objects by Name
- real-time
- Subvolume
- statistics
- Subvolume Statistics
- user-defined
- Subvolume
- subvolume command
- Creating Subvolumes
- subvolume
- subvolumes
- Multiple Address Spaces
- symbolic links
- Understand the Use of Symbolic Links and Device Names in Output
- sysadmdesktop
- Logging In
- sysctl
- Making Temporary Parameter Changes
- system dump analysis
- Using the System Dump Analysis Tool
- system log
- File Menu
- system log file
- File Menu
- system tunable kernel parameters
- appropriate settings
- Using Appropriate Parameter Settings
- permanent changes
- Making Permanent Parameter Changes
- queries
- Querying a Current Parameter Setting
- temporary changes
- Making Temporary Parameter Changes
- system tunable parameters
- RHEL
- Making Permanent Parameter Changes
- tasks
- Performing Tasks
- Tasks menu
- Tasks Menu
- tempname state
- Displaying the State of Volume Elements and Physvols
- term definitions
- Getting More Information
- tools
- system dump analysis
- Using the System Dump Analysis Tool
- topology
- creation
- Creating an XVM Topology Tree
- display
- Creating an XVM Topology Tree
- TP9100 and path failover
- TP9100 and RM610/660
- TP9300 and path failover
- TP9300, TP9500, TP9700, and S330
- TP9500 and path failover
- TP9300, TP9500, TP9700, and S330
- TP9700 and path failover
- TP9300, TP9500, TP9700, and S330
- tree view
- See view area
- troubleshooting
- GUI use
- Use XVM Configuration Tools Appropriately
- reporting problems to SGI
- Reporting Problems to SGI
- using SGI Knowledgebase
- Using SGI Knowledgebase
- tunable parameters
- Set Mirror Revive Resources Properly
- Slow Mirror Revives
- unlabel command
- Destroying Physvols
- Removing Disks from XVM with the unlabel
Command
- unlabeled disk
- Specifying Objects by Name
- Specifying Objects by Name
- definition
- XVM Objects
- user-defined subvolume
- Subvolume
- valid
- state
- Displaying the State of Volume Elements and Physvols
- /var/adm/SYSLOG
- File Menu
- /var/log/messages
- File Menu
- view area
- GUI Window Layout
- view cluster components
- View Menu
- view component details
- Viewing Component Details
- volume
- creation
- Creating Volumes
- Creating the Volume
- creation example
- Striping a Portion of a Disk
- definition
- Volume
- destruction
- Deleting Volume Elements
- display
- Displaying the State of Volume Elements and Physvols
- growing
- Growing the Volume
- limitations
- Subvolume
- Children
- logical levels
- Overview of XVM Volume Composition
- management
- Managing Logical Resources
- mirroring
- Mirroring Data on the Volume
- offline state
- Disabling Volume Elements
- Deleting Volume Elements
- online modification
- Online Modification of a Volume
- online state
- Disabling Volume Elements
- regenerating
- Saving and Regenerating an XVM Configuration
- reorganization
- Reorganizing Volumes
- writing data
- Writing Data
- volume command
- Creating Volumes
- volume
- volume element
- attaching
- Attaching Volume Elements
- automatic creation
- Automatic Creation of a Volume and Subvolume
- child syntax
- Specifying Objects by Piece Number
- creation
- Creating Logical Resources
- definition
- Overview of XVM Volume Composition
- XVM Objects
- detaching
- Detaching Volume Elements
- display
- Displaying the State of Volume Elements and Physvols
- empty volume element
- Creating an XVM Topology Tree
- growing online
- Making Online Changes
- limitations
- Children
- naming
- Naming Volume Elements
- piece syntax
- Specifying Objects by Piece Number
- volume header
- Volume
- volume name, temporary
- Automatic Creation of a Volume and Subvolume
- volume using a GPT label
- Overview of Using a GPT Label
- volume width
- Large Number of Volumes
- web-based version of the GUI
- Starting the GUI from the Web
- wildcard
- Regular Expressions
- wildcards, regular expressions
- Regular Expressions
- working set
- Show the Available Unlabeled Paths
- Set Appropriate affinity
Values for Non-ALUA LUNs
- ws
- Show the Available Unlabeled Paths
- xfsrestore
- XVM Configuration for Mixing SSD and HDD Media
- xvm command
- Management Tools
- abbreviations
- Command Abbreviation
- help
- Online Help for xvm CLI Commands
- keywords
- Command Abbreviation
- Naming Rules
- output
- Regular Expressions
- redirection
- Regular Expressions
- show
- Show the Available Unlabeled Paths
- syntax
- Command Abbreviation
- Syntax Rules
- xvm commands
- foconfig
- Pushing the Contents of the /etc/failover2.conf
File to the Kernel
- foswitch
- Setting All LUNs to the Preferred Path
- label
- Label the Paths
- probe
- Label the Paths
- reprobe
- Label the Paths
- XVM GUI
- CXFS GUI and
- XVM Manager and CXFS Manager
- drag-and-drop
- Using Drag-and-Drop
- icons
- Key to Icons and States
- states
- Key to Icons and States
- window
- GUI Window Layout
- XVM logical volume
- definition
- See volume
- XVM Manager Graphical User Interface (GUI)
- states
- Key to Icons and States
- XVM objects
- names
- Explicit and Temporary Names
- regular expressions
- Regular Expressions
- types
- Specifying Objects by Name
- XVM shortcuts
- Shortcuts Using Command Buttons
- XVM volume
- limitations
- Attaching Volume Elements
- saving
- Saving and Regenerating an XVM Configuration
- xvm_congestion_check
- xvm_congestion_check
- xvm_defeat_stripe_unit_in_min_io
- xvm_defeat_stripe_unit_in_min_io
- xvm_max_revive_rsc
- xvm_max_revive_rsc
- xvm_max_revive_threads
- xvm_max_revive_threads
- xvm_mr_daemon_max
- xvm_mr_daemon_max
- xvm_mr_daemon_min
- xvm_persistent_name_scan.sh
- Path Manager
- xvmgr
- Management Tools
- Starting the GUI via the Command Line
- See GUI