xortest
*> xortest
done
*> xortest –
Usage: xortest [-rnd][-t][-w][-x | -c | -none][-dp][-l n]
*> xortest
done
*> xortest –
Usage: xortest [-rnd][-t][-w][-x | -c | -none][-dp][-l n]
You can’t actually interact with the volumes, this is an old command that is superceded by aggr now.
*> vol
vol: Please use the “aggr” command for maintenance operations on traditional volumes and aggregates.
*> storage
usage: storage <subcommand>
subcommands are:
disable adapter <name>
enable adapter <name>
help <sub_command>
rename switch <oldname> <newname>
release disks
release { mc | tape } <name>
show adapter [ -a ] [ <name> ]
show initiators [-a]
show hub [ -a ] [ <hub-name> ]
show expander [ -a ] [ <expander-name> ]
show disk [ -a | -x | -p ] [ <name> ]
show fabric
show mc [ <name> ]
show port [ <name> ]
show switch [ <name> ]
show tape [ <name> ]
show tape supported [ -v ]
stats tape <name>
stats tape zero <name>
*> sesdiag
usage: sesdiag <subcommand>
subcommands are:
dump -h <channel> -s <shelf id> -p <page code>
The available page codes are 0×01, 0×02, 0×07, and 0×0a.
*> scsi
scsi — scsi testing utilities
usage: scsi <options>
NOTE: all <device_name> arguments are of the form:
<path_identifier>.<device_identifier>
where:
path_identifier is <switch:port> | <adapter>
device_identifier is <device_id[L<logical_unit_number>Options are:
capacity <device_name>
reads the capacity of a device
dumpfailures [-s] <device_name>
display failure information bytes read from disk
format <device_name> …
formats a device
inquiry [-s] <device_name>
retrieves inquiry data from the scsi device
verify [ -l lba ] [ -n <num_sectors> ] <device_name> …
verify a device
modeselect -p <page> {-o <offset> -v <value>}… <device_name>
sets the device parameter pages
modesense -p <page> [-t {current|changeable|default|saved}] <device_name>
returns the device parameter pages
readdefect [-b] -t {primary|grown} <device_name>
read in the defect list for the device
reset <device_name>
resets the device
start <device_name>
start up a device
stop <device_name>
stop a device
test [ -h <adapter> ] <device_name>
sends a test unit ready to the device
write_maint_file <filename>
reads a binary maintenance test result file and writes it to a text file
writefailure -u <device_name>
write unfail information to disk
drive_log [-p] <device_name | all>
Retrieves Health Trigger logs from the designated disk(s). The -p option retrieves partial log file(s).
*> sasstat
Usage: sasstat dev_stats [<adapter_name>]
sasstat adapter_state [<adapter_name>]
sasstat shelf [<adapter_name>]
sasstat shelf_short [<adapter_name>]
sasstat expander <adapter_name>[.<shelf_id>]
sasstat expander_map [<adapter_name>]
sasstat expander_phy_state [<adapter_name>[.<shelf_id>]]
Unfortunately I don’t have any SAS disks to play with at the moment. But I really want to know what “sasadmin sata_anarchy” does
*> sasadmin
Usage: sasadmin dev_stats [<adapter_name>]
sasadmin dev_phy_disable <adapter_name>.<shelf_id>.<bay_id>
sasadmin dev_phy_reset <adapter_name>.<shelf_id>.<bay_id>
sasadmin dev_phy_clear_affiliation <adapter_name>.<shelf_id>.<bay_id>
sasadmin dev_power_cycle <adapter_name>.<shelf_id>.<bay_id>
sasadmin adapter_phy_enable <adapter_name> <phy_num>
sasadmin adapter_phy_disable <adapter_name> <phy_num>
sasadmin expander_phy_disable <adapter_name>.<shelf_id> <phy_num>
sasadmin expander_profile_byte {{-h <adapter_name> -s <shelf_id>} | -w <shelf_wwn>} [-o <byte offset>] -v <ctrl value> -l <module id>
sasadmin expander_reset_count {{-h <adapter_name> -s <shelf_id>} | -w <shelf_wwn>} -l <module id>
sasadmin expander_cli <adapter_name>.<shelf_id>[.<module id>] “<command>”
sasadmin expander_ctrl {{-h <adapter_name> -s <shelf_id>} | -w <shelf_wwn>} [-p <phy number>] -v <ctrl value> -l <module id>
sasadmin expander_phy_reset <adapter_name>.<shelf_id> <phy_num>
sasadmin expander_phy_dongle_data <adapter_name>.<shelf_id> <phy_num>
sasadmin expander_phy_power_off <adapter_name>.<shelf_id> <phy_num>
sasadmin expander_phy_power_on <adapter_name>.<shelf_id> <phy_num>
sasadmin expander_phy_mux_reset <adapter_name>.<shelf_id> <phy_num>
sasadmin adapter_reset <adapter_name>
sasadmin adapter_offline <adapter_name>
sasadmin adapter_online <adapter_name>
sasadmin adapter_state [<adapter_name>]
sasadmin adapter_reservation_state <adapter_name>
sasadmin adapter_force_clear_reservations <adapter_name>
sasadmin adapter_force_rediscovery <adapter_name>
sasadmin expander <adapter_name>[.<shelf_id>]
sasadmin expander_map [<adapter_name>]
sasadmin expander_phy_state [<adapter_name>[.<shelf_id>]]
sasadmin expander_routes <adapter_name>.<shelf_id>
sasadmin shelf [<adapter_name>]
sasadmin shelf_short [<adapter_name>]
sasadmin channels
sasadmin sata_anarchy <adapter_name>.<shelf_id>.<bay_id> <subcommand>
*> raid_config
maximum disks possible 14
maximum raid groups possible 400
maximum traditional volumes and aggregates possible 200
maximum stripes possible 64
average raid group size 14
No. of disks in system 0
No. of groups in system 0
No. of traditional volumes and aggregates in system 0
Maximum write disks active 14
Maximum write groups active 1
Maximum reconstructs 2
Maximum reconstruction size 64
Maximum disk copy operations 4
RAID buffer reserve 8564
RAID adjust buffer reserve 0
average raid disk write queue length 50
average raid disk read queue length 50
average raid disk write transfer rate 50
average raid disk read transfer rate 100
*> fcstat
Usage: fcstat link_stats [<channel_name>]
fcstat fcal_stats [<channel_name>]
fcstat device_map [<channel_name>]
Bad Behavior has blocked 706 access attempts in the last 7 days.
© 2009-2010 Chris Kranz All Rights Reserved
This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.