This guide provides comprehensive information about the vSAN diagnostic options available in the user interface. These diagnostic tools enable system administrators to monitor, troubleshoot, and maintain vSAN deployments effectively.
Critical Warning
The diagnostic commands detailed in this guide are powerful administrative tools. Improper usage can result in:
- System outages
- Service interruptions
- Potential data loss
Exercise extreme caution and ensure proper understanding before execution.
To use these diagnostic tools, you must have:
- Root-level access to your VergeIO cluster
- Note: Tenants do not have a vSAN.
- Navigate to vSAN Diagnostics using either method:
Command Visibility
Enable the "Show Command" option to view the exact command being executed. This can be valuable for:
- SSH execution
- BASH script integration
- Advanced command automation
Running this command allows you to manually add a drive via the UI.
Drives are normally added either during the installation, or via the Nodes > Nodes Drives page.
However adding them in that way does not allow for the addition of drives to Tier0.
Prerequisites:
- Drive must be physically present in the system
- Drive must be visible from Nodes > Nodes Drives page
Usage Parameters:
- Selecting Add Drive to vSAN
- From the right menu, select the Node that we will be adding the drive to.
- Enter the appropriate path, E.G.
`/dev/nvme0n1```<br>
- You can use the "Click here to view devices" to get the path.
!!! warning "The contents of this drive will be overwritten."
- Select the Tier you want to assign the drive to.
- Check the Swap box if you want Swap enabled on this drive.
!!! info "This will use the cluster settings for the Swap size."
- Verify. You will need to TYPE Yes I know what I'm doing in the Verify box.
- Select SEND →
CLI Syntax:
vcmd newdevice --path=PATH [OPTIONS]
--path=PATH Path to target device
--tier=NUM Tier number assignment
Terminates any active integrity check operations. See Integrity Check for additional information.
CLI Syntax:
Reference counts are how the vSAN tracks the number of times a file is referenced in the vSAN.
Clearing this count will force a full vSAN walk and a refresh of the Reference Counts.
Function:
- Clears existing reference counts
- Initiates full vSAN traversal
- Rebuilds reference count data
Support Authorization Required
Execute only under direct support guidance.
Usage Parameters:
- Verify. You will need to TYPE Yes I know what I'm doing in the Verify box.
- Select SEND →
CLI Syntax:
Running this query will allow you to find out what an Inode (Index Node) referrences.
Inode is a data structure that stores information about a file or directory, such as its owner,
access rights, date and time of creation and modification, size and location on the vSAN.
Each file or directory in the system has its own unique index node number (inode number),
which can be used to perform various operations with a file or directory.
This can be used to troubleshoot errors in the vSAN.
Purpose:
- Retrieves inode reference information
- Maps inode numbers to filesystem entities
- Assists in vSAN troubleshooting
CLI Syntax:
find /vsan -inum inode_number_here -printf /%P\n
Retrieves detailed cache information for specified nodes.
Output Information:
- Total cache capacity
- Available cache space
- Cache page statistics
- Performance metrics
CLI Syntax:
Retrieves client connection information for specified nodes.
Output Information:
- Connected node information
- IP address mappings
- Worker thread statistics
CLI Syntax:
Retrieves cluster-wide performance metrics.
Output Information:
- Read/write rates
- Throttle status
- Performance statistics
CLI Syntax:
Provides cluster-wide storage utilization information.
Output Information:
- Maximum storage capacity
- Current utilization
- Repair operation counts
CLI Syntax:
Retrieves master node information from each cluster member.
Output Information:
- Master node identification
- Online status
- Transaction logging information
CLI Syntax:
Retrieves integrity check results for specified nodes.
CLI Syntax:
Provides comprehensive device inventory.
Output Information:
- Device identifiers
- System paths
- Tier assignments
CLI Syntax:
Retrieves detailed device status information.
Output Information:
- Device paths
- Operational status
- Capacity metrics
- Performance statistics
CLI Syntax:
Provides device utilization metrics.
Output Information:
- Total capacity
- Current utilization
- Usage trends
CLI Syntax:
Retrieves detailed file metadata.
Output Information:
- Inode information
- File type
- Tier assignment
- Hash key data
CLI Syntax:
vcmd stat /path/to/file.raw
Retrieves FUSE (Filesystem in Userspace) statistics.
Output Information:
- Mount point information
- Thread statistics
- Throttling metrics
CLI Syntax:
Retrieves results from the most recent integrity check.
Output Information:
- Check status
- Path information
- Temporal data
- Verification results
CLI Syntax:
Retrieves journal system status information.
Output Information:
- Operational status
- Redundancy status
- System metadata
CLI Syntax:
Retrieves detailed hardware information for storage devices.
Output Information:
- Driver information
- Model specifications
- Firmware versions
- Physical attributes
CLI Syntax:
Retrieves comprehensive node configuration data.
Output Information:
- Node identification
- Cluster configuration
- System parameters
- Operational status
CLI Syntax:
Provides cluster-wide node inventory.
Output Information:
- Node identification
- Online status
- Version information
- Tier utilization
CLI Syntax:
Resolves filesystem paths from inode numbers.
CLI Syntax:
Retrieves read-ahead buffer statistics.
Output Information:
- Queue statistics
- Thread utilization
- System status
CLI Syntax:
Monitors ongoing repair operations.
Output Information:
- Device repair status
- Operation progress
- System health
CLI Syntax:
Retrieves active system configuration.
Output Information:
- Worker thread allocation
- System throttles
- Operational parameters
CLI Syntax:
Monitors synchronization operations.
Output Information:
- Operation frequency
- Start times
- File processing status
CLI Syntax:
Retrieves tier-to-device mapping information.
Output Information:
- Physical device mappings
- Tier assignments
- System configuration
CLI Syntax:
Retrieves tier-to-node mapping information.
Technical Details:
- Base-0 indexing (0=Node1, 1=Node2, etc.)
- 65536 buckets per tier map
- Primary (tier_x.0) and redundant (tier_x.1) mappings
CLI Syntax:
Retrieves comprehensive tier health information.
Output Information:
- Redundancy status
- Walk statistics
- Transaction data
- Health metrics
CLI Syntax:
Monitors real-time I/O statistics.
Real-time Data
Multiple executions may be necessary for trend analysis.
CLI Syntax:
vcmd getfhlist | grep -Eo '(ino|rrate|wrate)\b.*'
Retrieves detailed volume utilization statistics.
Parameters:
- Path specification (optional)
- Recursive flag
- Human-readable output
- Preferred tier display
CLI Syntax:
vcmd getvolusage --path=/ --recursive=1 --human=1
Initiates system integrity verification.
Parameters:
- Path specification (required)
- Recursive operation
- Fix mode (destructive)
- Meta-tier only option
Data Loss Risk
Fix mode zeros bad blocks. THIS IS DESTRUCTIVE. Use only under support guidance.
CLI Syntax:
Performs device-level integrity verification.
Parameters:
- Node selection
- Device ID (-1 for all devices)
CLI Syntax:
vcmd integcheckdevice --id=x
Generates storage utilization summaries.
Parameters:
- Path specification
- Recursive operation
- Preferred tier display
- Deduplication analysis
- Fast deduplication option
CLI Syntax:
Need Help?
If you need further assistance or have any questions about this article, please don't hesitate to reach out to our support team.
- Last Updated: 2024-12-27
- VergeOS Version: 4.13.2