|Main index||Section 8||Options|
Currently one global option is supported:
|unit specifies the unit of the controller to work with. If no unit is specified, then unit 0 is used.|
Volumes may be specified in two forms. First, a volume may be identified by its location as [xx:]yywhere xx is the bus ID and yy is the target ID. If the bus ID is omitted, the volume is assumed to be on bus 0. Second, on the volume may be specified by the corresponding daX device, such as da0.
The mpt(4) controller divides drives up into two categories. Configured drives belong to a RAID volume either as a member drive or as a hot spare. Each configured drive is assigned a unique device ID such as 0 or 1 that is show in show config, and in the first column of show drives. Any drive not associated with a RAID volume as either a member or a hot spare is a standalone drive. Standalone drives are visible to the operating system as SCSI disk devices. As a result, drives may be specified in three forms. First, a configured drive may be identified by its device ID. Second, any drive may be identified by its location as xx:yywhere xx is the bus ID and yy is the target ID for each drive as displayed in show drives. Note that unlike volumes, a drive location always requires the bus ID to avoid confusion with device IDs. Third, a standalone drive that is not part of a volume may be identified by its corresponding daX device as displayed in show drives.
The mptutil utility supports several different groups of commands. The first group of commands provide information about the controller, the volumes it manages, and the drives it controls. The second group of commands are used to manage the physical drives attached to the controller. The third group of commands are used to manage the logical volumes managed by the controller. The fourth group of commands are used to manage the drive configuration for the controller.
The informational commands include:
|Displays the version of mptutil.|
|Displays information about the RAID controller such as the model number.|
|Displays the volume and drive configuration for the controller. Each volume is listed along with the physical drives that the volume spans. If any hot spare drives are configured, then they are listed as well.|
|Lists all of the physical drives attached to the controller.|
|Display all the entries from the controller's event log. Due to lack of documentation this command is not very useful currently and just dumps each log entry in hex.|
|Lists all of the logical volumes managed by the controller.|
The physical drive management commands include:
|Mark drive as "failed requested". Note that this state is different from the "failed" state that is used when the firmware fails a drive. Drive must be a configured drive.|
|Mark drive as an online drive. Drive must be part a configured drive in either the "offline" or "failed requested" states.|
|Mark drive as offline. Drive must be a configured, online drive.|
The logical volume management commands include:
|name volume name|
|Sets the name of volume to name.|
|volume cache volume enable|disable|
|Enables or disables the drive write cache for the member drives of volume.|
|volume status volume|
|Display more detailed status about a single volume including the current progress of a rebuild operation if one is being performed.|
The configuration commands include:
|clear||Delete the entire configuration including all volumes and spares. All drives will become standalone drives.|
|raid0||Creates one RAID0 volume spanning the drives listed in the single drive list.|
|raid1||Creates one RAID1 volume spanning the drives listed in the single drive list.|
|Creates one RAID1E volume spanning the drives listed in the single drive list.|
Note: Not all volume types are supported by all controllers.
|Delete the volume volume. Member drives will become standalone drives.|
|add drive [volume]|
|Mark drive as a hot spare. Drive must not be a member of a volume. If volume is specified, then the hot spare will be dedicated to that volume. Otherwise, drive will be used as a global hot spare backing all volumes for this controller. Note that drive must be as large as the smallest drive in all of the volumes it is going to back.|
|Remove the hot spare drive from service. It will become a standalone drive.|
Create a RAID1 array from the two standalone drives da1 and da2:
Mark standalone drive da3 as a global hot spare:
Drive configuration commands result in an excessive flood of messages on the console.
The mpt version 1 API that is used by mptutil and mpt(4) does not support volumes above two terabytes. This is a limitation of the API. If you are using this adapter with volumes larger than two terabytes, use the adapter in JBOD mode. Utilize geom(8), zfs(8), or another software volume manager to work around this limitation.
|MPTUTIL (8)||August 16, 2009|
|Main index||Section 8||Options|