.\" cvadmin.8: auto-generated, DO NOT EDIT
.\"
.\" Copyright 1998-2024. Quantum Corporation. All Rights Reserved.
.\" StorNext is either a trademark or registered trademark of
.\" Quantum Corporation in the US and/or other countries.
.\"
.\" Code start macro
.de Cs
.sp
.ft C
.in +0.3i
.nf
..
.\" Code end macro
.de Ce
.fi
.in -0.3i
.ft R
..
.TH CVADMIN 8 "September 2024" "Xsan File System"
.SH NAME
cvadmin \- Administer an Xsan File System
.SH SYNOPSIS
.na
.nh
.HP
.B cvadmin
.RB [ \-H \ \fIFSMHostName\fP]
.RB [ \-F \ \fIVolumeName\fP]
.RB [ \-M ]
.RB [ \-n ]
.RB [ \-x ]
.RB [ \-f \ \fIfilename\fP]
.RB [ \-e \ \fIcommand1\fP \ -e \ \fIcommand2\fP...]
.ad
.hy
.SH DESCRIPTION
\fBcvadmin\fR is an interactive command used for general purpose 
administration of an Xsan volume including:
.PP
1. displaying file system and client status
.PP
2. activating a file system currently in stand-by mode
.PP
3. viewing storage pool attributes
.PP
4. enabling File System Manager (FSM) tracing
.PP
5. displaying disk and path information for the local system
.PP
6. forcing FSM failover
.PP
7. fetching FSM usage and performance statistics
.PP
8. temporarily enabling or disabling global file locking
.PP
9. generating a report of open files
.PP
10. listing currently held file locks
.PP
11. starting, restarting and stopping of daemon processes
.PP
12. resetting RPL information
.SH OPTIONS
Invoke \fBcvadmin\fR to start the interactive session and 
list the running File System Managers (FSMs).  
(Note: Xsan system 
services must be started prior to running \fBcvadmin\fR.  In particular,
the local
.BR fsmpm (8)
process must be active.)
.PP
The initial output shows the running FSMs grouped by the cluster in
which they are located. The hostnames or IP addresses are those that
are advertised to clients. When more than one location is listed,
one or more these will be marked as preferred. This means that
this address is on the metadata network and should be used,
if possible, by a client to make a connection to the FSM. The
remaining addresses can be used if a connection can not be
made using a preferred address.
.PP
Note: An administrator can filter out
addresses that are not to be advertised by using the
.BR snfs_metadata_network_filter.json (5)
configuration file.
.PP
Then (optionally) use the \fBselect\fR command described below to pick 
an FSM to connect to.  Once connected, the command will display basic 
information about the selected volume and prompt for further commands.
.PP
Note that a few commands such as \fBpaths\fR, \fBdisks\fR, 
\fBstart\fR, and \fBstop\fR
require information obtained from the local
.BR fsmpm (8)
only, so there is is no need to select an FSM prior to using them.
.SH USAGE
.IP "\fB\-H\fP \fIFSMHostName\fP"
Connect to the FSM located on the machine FSMHostName. By default cvadmin will attempt to connect to an FSM located on the local machine.
.IP "\fB\-F\fP \fIVolumeName\fP"
Automatically set the volume \fIVolumeName\fR as the active
volume in cvadmin.
.IP \fB-M\fR
When listing file systems with the \fBselect\fR command, display [managed]
next to each file system with DataMigration enabled.  This option is 
currently only intended for use by support personnel.
.IP "\fB\-f\fP \fIfilename\fP"
Read commands from \fIfilename\fR
.IP "\fB\-e\fP \fIcommand\fP"
Execute command(s) and exit
.IP \fB\-n\fR
Show numerical addresses instead of trying to determine symbolic host
.IP \fB\-x\fR
Enable extended commands.
.SH COMMANDS
The \fBcvadmin\fR commands can be used to display and modify the Xsan active
configuration. When a modification is made, it exists only as long as the
\fBFSM\fR is running. More permanent changes can be made in the configuration
file. Refer to the
.BR snfs_config (5)
man page for details. The following
commands are supported.
.sp
The syntax for \fIvolume_name\fP is:
.IR name [ \fB@\fPcluster [ \fB/\fPaddom ]]
.sp
.IP "\fBactivate\fP \fIvolume_name \fP[\fIhostname_or_IP_address\fP]"
Activate a volume \fIvolume_name\fR.
This command may cause an FSM to activate.
If the FSM is already active, no action is taken.
.IP "\fBactivate\fP \fIvolume_name number_of_votes\fP"
Apple Internal only.  Bypass the election system and attempt to
activate the fsm on this node.
.IP "\fBcluster\fP \fBselect\fP [\fIN\fP|[\fB+\fP]\fIcluster_name\fP]"
Select a cluster to be used by other commands
when the cluster name isn't explicitly given with
the FSM name.  Normally only a known cluster name
can be selected, but preceding it with a '\fB+\fP' will
force an unknown cluster name to be used.
A cluster name of
.BR none " or " 0
will de-select the
currently selected cluster name.
Using no arguments or just \fBselect\fP will show all
known clusters.
\fICluster_name\fP is
.RB [ @ ] \fIcluster\fP [ /\fIaddom\fP ].
.IP "\fBcluster\fP \fBfilter\fP [\fIN\fP|\fIcluster_name\fP]"
Set a filter for the output of the \fBselect\fP command.
When a cluster filter is set, only FSMs in that cluster
will be displayed by \fBselect\fP.  The filter can be set
to all the clusters in an administrative domain by
using
.BR "\"cluster filter /" \fIaddom\fP\".
A cluster name of
.BR none " or " 0
will disable the filter.
Using no arguments or just \fBfilter\fP will show all
known clusters.
\fICluster_name\fP is
.RB [ @ ] \fIcluster\fP [ /\fIaddom\fP ].
.IP "\fBcoord\fP [[\fBon\fP] \fIhostname_or_IP_address\fP]"
Display the list of NSS coordinators on the
local host or on the specified host.
.IP "\fBclientunmount\fP \fIgentle_time_in_seconds\fP"
.IP "\fBclientunmount hard\fP \fIgentle_time_in_seconds force_time_in_seconds\fP"
Instruct clients of the selected volume to unmount. The first form
of the command waits \fIgentle_time_in_seconds\fP seconds for clients to
unmount the volume. Clients receive a message from the fsm directing
them to normally unmount the volume.  During this time, no new
client connections are permitted. If all clients unmount within
that time, the fsm continues with new connections forbidden.
.sp
In the second form of the command, the fsm moves to a second stage
if any clients fail to unmount. In this stage, clients are instructed
to unmount the volume forcibly. The fsm waits \fIforce_time_in_seconds\fP
seconds, and then completes the operation. Client connections
remain forbidden at the end of this operation.
.sp
After completing this command, the administrator should stop the
volume.
.IP "\fBdebug\fP [[\fB+\fP|\fB-\fP] \fIflag\fP [ ... ]]"
View or set the File System Manager's debugging flags. Entering the command
with no \fIflag\fR will return current settings, the location of the
\fBFSM\fR log file and a legend describing what each setting does.
By entering the command with a \fIflag\fP list, the \fBFSM\fR Debugging Flags
will be set accordingly.
Each \fIflag\fP can be either a name or numeric value.
Names will be mapped to their numeric value, and may be
abbreviated as long as they remain unique.
Numeric values are specified using a standard decimal
or hexadecimal (0x) value of up to 32 bits.
Using '\fB+\fR' or '\fB-\fR'
enables ('\fB+\fR') or disables ('\fB-\fR')
only the selected flags, leaving all other flags unchanged.
.sp
\fBNOTE\fR - Setting Debugging Flags will severely impact the \fBFSM\fR's
performance!
Do this only when directed by a Apple specialist.
.TP
.IP \fBdiscon\fR
Forcefully disconnect a client from the FSM.
With no arguments, \fBdiscon\fR displays the list of
connected clients. When supplied an index, \fBdiscon\fR
will immediately disconnect the specified client.
Only use when recommended by Technical Support.
Also see the "repblocked" command.
.TP
.BR "disks " [ refresh ]
Display the Xsan disk volumes local to the system that cvadmin is
attached to. Using the optional \fBrefresh\fR argument will force the
fsmpm to re-scan all volumes before responding. If the fsmpm's view of
the disks in any file system changes compared with the FSM's view of
that client's disks as a result of the refresh, a disconnect and reconnect
to the FSM will take place to resynchronise the file system state.
.TP
.BR "disks " [ refresh "] \fIfsm\fP"
Display the Xsan meta-data disk volumes in use by the \fIfsm\fR.
If the optional \fBrefresh\fR argument is used, additional paths
to these volumes may be added by the fsm.
.TP
.RI "\fBfail\fP " [volume_name | index_number]
Initiate an FSM Failover of volume \fIvolume_name\fP. This command 
may cause a stand-by FSM to activate. If an FSM is already active, the FSM 
will shut down. A stand-by FSM will then take over. If a stand-by FSM is
not available the primary FSM will re-activate after failover processing
is complete.
.TP
.BR "files"
Report counts of files, directories, symlinks and other objects
which are anchored by a user type inode. These include named streams,
block and character device files, fifos or pipes and named sockets.
If the file system is undergoing conversion to StorNext 5.0,
conversion progress is displayed and counters reflect
the count of converted objects.
.TP
.RI "\fBfsmlist\fP [" volume_name "] [ \fBon\fP " hostname_or_IP_address ]
Display the state of FSM processes, running or not.  Optionally specify 
a single \fIvolume_name\fR to display.  Optionally specify the host
name or IP address of the system on which to list the FSM processes.
.IP \fBfilelocks\fR
Query cluster-wide file/record lock enforcement.
Currently cluster-wide file locks are automatically used on Unix.
Windows file/record locks are optional.
.sp
If enabled, byte-range file locks are coordinated through the FSM,
allowing a lock set by one client to block overlapping locks by other
clients.
If disabled, then byte-range locks are local to a client
and do not prevent other clients from getting byte-range locks on a file,
however they do prevent overlapping lock attempts on the same client.
.TP
.BR "help " ( ? )
The \fBhelp\fR or \fB?\fR command will display a command usage summary.
.TP
.BR "latency-test " [\fIindex_number\fP| all "] [\fIseconds\fP]"
Run an I/O latency test between the FSM process and one client or all clients.
The default test duration is 2 seconds.
.TP
.BR "metadata"
Report metadata usage.  Also provide an estimate on the value of 
bufferCacheSize that will allow all metadata to be cached.
.TP
.BR "mdarchive [\fIstatus\fR|\fIbackup\fR|\fIrebuild\fR|\fIprune\fR|\fIthrottle\fR]"
Run commands targeting the metadata archive associated with the selected FSM.
Running mdarchive without command arguments will display the full path
location of the metadata archive.
.TP
.BR "mdarchive status"
The \fIstatus\fR command prints the progress of the current metadata archive
activity, if any. If generating a new metadata archive or restoring an
existing one, the percentage complete will be displayed. Otherwise, the
current update backlog is displayed.
.TP
.BR "mdarchive rebuild [new]"
If metadataArchiveDays is set to zero then the \fIrebuild\fR command will
force the FSM to discard the existing metadata archive and generate a
new one, otherwise the FSM will rebuild the existing metadata archive in a
way that will preserve history across the rebuild. Rebuilds can be performed
online while clients are active in the file system.

When metadataArchiveDays is set to a value greater than zero, requesting a
\fInew\fR rebuild will cause the FSM to delete the current metadata archive
before starting the rebuild. All metadata history that existed prior to the
new rebuild will be lost but the rebuild will shrink the mdarchive down to its
minimum size. Requesting a \fInew\fR rebuild has no effect when
metadataArchiveDays is set to zero because the existing metadata archive is
always deleted before starting the rebuild in that case.

WARNING: When using the \fInew\fR argument to the rebuild command, all
metadata history that existed prior to the rebuild will be lost. This
will prevent external applications like snaudit and snhistory from
reporting events that occurred prior to the rebuild and will prevent
snrecover from recovering files that were deleted prior to the rebuild.
.TP
.BR "mdarchive rebuild wait"
Wait for an ongoing rebuild to complete and report status periodically.
.TP
.BR "mdarchive backup [\fIfull\fR|\fIpartial\fR] pathname"
For an FSM with a current mdarchive, request a backup copy be generated
as a compressed tar file.
The pathname must specify an existing directory on the FSM node and include
the file name to be created.
A full dump contains all the content, a partial dump contains all the content
changed since the last backup.
.TP
.BR "mdarchive backup wait"
Wait for an ongoing mdarchive backup to complete and report progress periodically.
.TP
.BR "mdarchive prune"
The \fIprune\fR command will force the removal of expired historical data
from the metadata archive. This command is ignored and a message is written
to the system log file if metadataArchiveDays is set to zero in the
configuration file or if it is issued while an mdarchive build, file recovery,
or metadata restore is in progress.
.TP
.BR "mdarchive throttle set <threshold> <delay>"
Set the threshold (number of bundles) and delay (milliseconds) for
throttling incoming metadata changes to allow an
update backlog to dissipate. Throttling is disabled when
delay is equal to 0 which is the default.
In addition to using the cvadmin mdarchive command,
throttling can be set at FSM startup using the MDARCHIVE_THROTTLE_THRESHOLD
and MDARCHIVE_THROTTLE_DELAY environment variables.
Note: this option is not intended for general use. Only
enable throttling when recommended by Technical Support.
Note: the throttling capability may change or be removed
in a future release.
.TP
.BR "mdarchive throttle show"
Display current mdarchive throttle settings. See
"mdarchive throttle set" above.
.TP
.BI paths
Display the Xsan disk volumes visible to the local system.
The display is grouped by \fI<controller>\fR identity, and will
indicate the "Active" or "Passive" nature of the path if the Raid
Controller has been recognized as configured in Active/Active mode
with AVAT enabled.
.TP
.BR "proxy " [ long ]
Display Disk Proxy servers and optionally display the disks they serve for 
this volume.
.TP
\fBproxy who\fP \fIhostname\fP
The "who" option displays all proxy connections for the specified host.
.TP
.B qbm \fBtrace\fP [\fIclientid\fP]
Create a QBM internal trace file on the MDC.
If \fIclientid\fP is specified (where \fIclientid\fP is the client's login id),
a client trace is also also generated.  This command creates an SNQBM_xxx
file in the debug directory.  Currently, only Windows clients generate
internal traces.  This command is for Quantum use only.
.TP
.B qbm \fBshow\fP \fIstripe-group-num\fP
Show the QBM allocation table for a stripe group given the stripe-group
index.  All bandwidth (BW) is in MB/sec.  The display includes the following
sub-tables:

Stripe Group (SG) Table: SG max (capacity), BW currently free, the
total BW in the reserve pools, and the total over-subscripted (over capacity)
amount.

Priority (Pri) Table: table class name, count of clients in the
priority, total bandwidth allocated at this priority, minimum BW, maximum BW,
extra (over min) BW, reserved BW used/total reserve allocated to this priority,
and current BW used.

Client Entry: list number, IP address, client login number, bandwidth
information - minimum, maximum and current BW, restore BW,
flag (l - client asked for less, m - client asked for more, g - client given
more BW over minimum BW).
.TP
.B qbm \fBnewconfig\fP
Re-read the <\fI_file_system_name_\fR>_qbm.conf file and update the clients.
.TP
.B qos
Display per-stripe group QOS statistics.
Per-client QoS statistics are also displayed under each qos-configured stripe group.
.TP
.B quit
This command will disconnect \fBcvadmin\fR from the \fBFSM\fR and exit.
.TP
\fBras enq [ nomerge ]\fP \fIevent "detail string"\fP
Generate an SNFS RAS event.  If "nomerge" is specified, multiple instances of the RAS event are not merged into a single ticket.  For internal use only.
.TP
\fBras enq [ nomerge ]\fP \fIevent reporting_FRU violating_FRU "detail string"\fP
Generate a generic RAS event.  If "nomerge" is specified, multiple instances of the RAS event are not merged into a single ticket.  For internal use only.
.TP
\fBregapigw\fP
Register the filesystem with the fsmpm to enable registration with an api
gateway.  To be used when the fsmpm is not aware of this filesystem for api
gateway registration purposes.  This can be confirmed using the 'snrest gateway
status -d' command and noting the absence of the filesystem.  The fsmpm performs the api gateway registration
on behalf of the filesystem.  This situation should not occur, but if it does
this command allows recovery from the situation without requiring a restart of
the filesystem.
.IP \fBrepblocked\fR
Generate a report of files that may be causing open operations to block
due to an unresponsive client that is slow to acknowledge a request to
change state.  Such clients should be inspected to determine whether
there is a reason for their lack of response. One common cause of
unresponsiveness is that Xsan clients have entered sleep mode. The
settings on these clients should be adjusted so they never sleep. If
the client is known to be hung, the connection to the FSM can be reset
using the \fBdiscon\fR command.
.IP \fBrepfl\fR
Generate a report that displays the file locks currently held.  Note:
this command is only intended for debugging purposes by support personnel.
In future releases, the format of the report may change or the command
may be removed entirely. Running the repfl command will write out a report file 
and display the output
filename.
.IP \fBrepof\fR
Generate a report that displays all files that are currently open on each Xsan
client.
Running the repof command will write out a report file and display the output
filename containing that report.
.br
The information displayed for each file is:
the pathname, inode number, the number of "writers" (which is the # of times this client has opened
the file for write -- usually 1 or 0), and stat information.
.br
Next a line is printed showing the open state across all clients.
The open state contains: the \fBcount\fP of different clients with this file open,
the # of those clients that are \fBwriters\fP, and which \fBclient\fP, if non-zero, has the file
open exclusively or that owns the \fBioToken\fP.
The open state \fBflags\fP are displayed followed by a set of strings indicating
the meaning of some of the bits in the \fBflags\fP field.
Some examples:
.sp
flags 0x2000: shared_read
.br
flags 0x5000: I/O token shared_excl
.br
flags 0x5009: revoking I/O token shared_excl
.br
flags 0x9: revoking OLD Exclusive
.sp
If \fBrevoking\fP is indicated, that means the \fBclient\fP(s) has been
sent a message and a response is being awaited.
If \fBclient\fP is zero with \fBrevoking\fP, a message was sent to one or more clients in \fBshared_read\fP.
.br
See also the \fBrepblocked\fP command.
.sp
In future releases, the format of the report may change.
.TP
.BR "resetrpl " [ clear ]
Repopulate Reverse Path Lookup (RPL) information.
The optional \fIclear\fR argument causes existing
RPL data to be cleared before starting repopulation.
Note: \fBresetrpl\fR is only available when cvadmin is
invoked with the \fB-x\fR option.  Running \fBresetrpl\fR
may significantly delay FSM activation.  This command
is not intended for general use.  Only run \fBresetrpl\fR
when recommended by Technical Support.
.TP
.BR restartd " \fIdaemon\fP [" once ]
Restart the \fIdaemon\fR process. 
For internal use only.
.TP
\fBselect \fR[\fIvolume_name\fR|\fIN\fR]
Select an active FSM to view and modify.  If no argument is
specified, a numbered list of FSMs and running utilities will
be displayed. If there is only one active volume in
the list, it will automatically be selected.
.sp
When a running utility is displayed by the select command, it
will show the following information. First the name of the file
system is displayed. Following that, in brackets "[]", is the name
of the utility that is running. Third, a letter indicating the access
type of the operation. The options here are (W) for read-write access,
(R) for read-only access and (U) for unique access. Finally, the location
and process id of the running utility is displayed.
.sp
If \fIvolume_name\fR is specified, then \fBcvadmin\fR will
connect to the current active FSM for that volume.
If \fIN\fR (a number) is specified, cvadmin will connect
to the \fIN\fRth FSM in the list.  However, only active FSMs may
be selected in this form.
.TP
\fBshow\fP [\fIpoolname\fP] [\fBlong\fP]
Display information about the storage pools associated with the selected
volume. If a storage pool name \fIpoolname\fR is given only that 
storage pool's information will be given. Omitting the \fIpoolname\fR 
argument will display all storage pools associated with the active file 
system. Using the \fBlong\fR modifier will additionally display
detailed information about the disk units associated with displayed
storage pools.
.TP
\fBstart\fP \fIvolume_name\fP [\fBon\fP \fIhostname_or_IP_address\fP]
Start a File System Manager for the volume \fIvolume_name\fR. 
When the command is running on an MDC of an HA cluster,
the local FSM is started,
and then an attempt is made to start the FSM on the peer MDC
as identified by the \fI/Library/Preferences/Xsan/ha_peer\fR file.
When the optional \fIhostname_or_IP_address\fR is specified,
the FSM is started on that MDC only.
The volume's 
configuration file must be operational and placed in 
\fI/Library/Preferences/Xsan/<volume_name>.cfg\fR before invoking this command.
See
.BR snfs_config (5)
for information on how to create a configuration file
for an Xsan volume.
.TP
\fBstartd\fP \fIdaemon\fP [\fBonce\fP]
Start the \fIdaemon\fR process. 
For internal use only.
.TP
\fBstat\fR
Display the general status of the volume. The output will show the 
number of clients connected to the volume. This count includes any
administrative programs, such as \fBcvadmin\fR. Also shown are some of
the static file-system-wide values such as the block size, number of
storage pools, number of mirrored storage pools and number of 
disk devices.
The output also shows total blocks and free blocks for the entire 
volume.
.TP
\fBstats\fP \fIclient_IP_address\fP [\fBclear\fP]
Display read/write statistics for the selected file system.
This command connects to the host FSMPM who then collects statistics
from the file system client. The ten most active files by bytes
read and written and by the number of read/write requests are
displayed.  If clear is specified, zero the stats after printing.
.TP
\fBstop\fP \fIvolume_name\fP [\fBon\fP \fIhostname_or_IP_address\fP]
Stop the File System Manager for \fIvolume_name\fR.
This will shut down the FSM for the specified volume on every MDC.
When the optional hostname or IP address is specified,
the FSM is stopped on that MDC only.
Further operations to the volume
will be blocked in clients until an FSM for the volume is activated.
.TP
\fBstopd\fP \fIdaemon\fP
Start the \fIdaemon\fR process. 
For internal use only.
.TP
\fBwinidmap\fP \fI__username__\fP
Show the MDC-mapped user id and group information for the username.
.TP
\fBwho\fR
Query client list for the active volume. The output will show the 
following information for each client.
.sp
Type      -  Type of connection. The client types are: 
.br
.in +0.3i
FSM - File System Manager(FSM) process
.br
ADM - Administrative(cvadmin) connection
.br
CLI - Volume client connection. May be followed by a CLI
      type character:
      S - Disk Proxy Server
      C - Disk Proxy Client
      H - Disk Proxy Hybrid Client. This is a client that has
          been configured as a proxy client but is operating
          as a SAN client.
.in -0.3i
.br
Location  - The client's hostname or IP address that was used by this client
to connect to the FSM.
.br
Up Time   - The time since the client connection was initiated
.SH EXAMPLES
Invoke the \fBcvadmin\fR command for volume named \fBsnfs1\fR.
.Cs

[root@dev-snc-daiquiri-n1 debug]# cvadmin -F snfs1
StorNext Administrator

Enter command(s)
For command help, enter "help" or "?".

List FSS

File System Services (* indicates service is in control of FS):
Selected Cluster: _cluster0/_addom0

Cluster: _cluster0/_addom0
 1>*fs1-man[0]           located on dev-snc-daiquiri-n1.mdh.quantum.com:52006 (pid 31711)
                         located on Qnode1:52006
                         located on 169.254.21.1:52006
                         located on 192.168.21.11:52006 [preferred]
 2> fs1-man[0]           located on dev-snc-daiquiri-n2.mdh.quantum.com:52004 (pid 42977)
                         located on 172.18.0.1:52004
                         located on 172.17.0.1:52004
                         located on Qnode2:52004
                         located on 169.254.21.2:52004
                         located on 192.168.21.12:52004 [preferred]
 3>*shared-SV1535CKH00012[0] located on dev-snc-daiquiri-n1.mdh.quantum.com:52003 (pid 23220)
                         located on Qnode1:52003
                         located on 169.254.21.1:52003
                         located on 192.168.21.11:52003 [preferred]
 4> shared-SV1535CKH00012[0] located on dev-snc-daiquiri-n2.mdh.quantum.com:52003 (pid 42382)
                         located on 172.18.0.1:52003
                         located on 172.17.0.1:52003
                         located on Qnode2:52003
                         located on 169.254.21.2:52003
                         located on 192.168.21.12:52003 [preferred]

Cluster: cluster1/_addom0
 5>*shared[0]            located on jk-rh6sp6-1.mdh.quantum.com:52003 (pid 8650)
 6> shared[0]            located on jk-rh6sp6-2.mdh.quantum.com:52003 (pid 19417)
 7>*snfs1[0]             located on jk-rh6sp6-1.mdh.quantum.com:52004 (pid 8651)
 8> snfs1[0]             located on jk-rh6sp6-2.mdh.quantum.com:52004 (pid 19431)

Select FSM "snfs1"

 Created           :    Wed Sep 26 12:27:43 2018
 Active Connections:    2
 Fs Block Size     :    4K
 Msg Buffer Size   :    8K
 Disk Devices      :    6
 Stripe Groups     :    3
 Fs Blocks         :    2684342720 (10.00 TB)
 Fs Blocks Free    :    2679776316 (9.98 TB) (99%)


snadmin (snfs1@cluster1/_addom0) >

.Ce
.PP
Show all the storage pools in the volume;
.Cs
snadmin (snfs1@cluster1/_addom0) > show
Show stripe groups (File System "snfs1@cluster1/_addom0")

Stripe Group 0 [sg0]  Status:Up,MetaData,Journal,Exclusive
  Total Blocks:536868544 (2.00 TB)  Reserved:0 (0.00 B) Free:536841775 (2.00 TB)
(99%)
  MultiPath Method:Rotate
    Primary  Stripe [sg0]  Read:Enabled  Write:Enabled

Stripe Group 1 [sg1]  Status:Up
  Total Blocks:1610605632 (6.00 TB)  Reserved:1082880 (4.13 GB) Free:1607753562
(5.99 TB) (99%)
  MultiPath Method:Rotate
    Primary  Stripe [sg1]  Read:Enabled  Write:Enabled

Stripe Group 2 [sg2]  Status:Up
  Total Blocks:1073737088 (4.00 TB)  Reserved:1082880 (4.13 GB) Free:1072022754
(3.99 TB) (99%)
  MultiPath Method:Rotate
    Primary  Stripe [sg2]  Read:Enabled  Write:Enabled


snadmin (snfs1@cluster1/_addom0) >

.Ce
.PP
Display the \fBlong\fR version of the \fBsg2\fR storage pool;
.Cs

snadmin (snfs1@cluster1/_addom0) > show sg2 long
Show stripe group "sg2" (File System "snfs1@cluster1/_addom0")

Stripe Group 2 [sg2]  Status:Up
  Total Blocks:1073737088 (4.00 TB)  Reserved:1082880 (4.13 GB) Free:1072022754 (3.99 TB) (99%)
  MultiPath Method:Rotate
  Stripe Depth:2  Stripe Breadth:64 blocks (256.00 KB)
  Affinity Key:af1
  Realtime limit IO/sec:0 (~0 mb/sec) Non-Realtime reserve IO/sec:0
    Committed RTIO/sec:0 Non-RTIO clients:0 Non-RTIO hint IO/sec:0
  Disk stripes:
    Primary  Stripe [sg2]  Read:Enabled  Write:Enabled
      Node 0 [t1_0008]
      Node 1 [t1_0009]


snadmin (snfs1@cluster1/_addom0) >

.Ce
.SH FILES
.I /Library/Preferences/Xsan/*.cfg
.SH "SEE ALSO"
.BR cvfs (8),
.BR snfs_config (5),
.BR snfs_metadata_network_filter.json (5),
.BR fsmpm (8),
.BR fsm (8),
.BR mount_acfs (8),
.BR sgmanage (8)