Controller Object Commands
www.3ware.com
41
Note:
If you are adding new drives, add them physically before issuing the
rescan commands. Hot swap carriers are required unless you first power-
down the system to prevent system hangs and electrical damage.
Example:
//localhost> /c1 rescan
Rescanning controller /c1 for units and drives ...Done
Found following unit(s): [/c1/u3]
Found following drive(s): [/c1/p7, /c1/p8]
Note:
Rescanning does not import non-JBOD on 7000/8000 models.
/cx commit
This command only applies to the Windows operating system. It commits all
changes if a faster shutdown method is needed when running certain database
applications. Linux and FreeBSD file systems do not require this command
since they have their own ways of notifying the controller to do clean up for
shut down.
/cx flush
This command forces the controller to write all cached data to disk for the
specified controller.
/cx show alarms [reverse]
Asynchronous events (also referred to as AENs or alarms) are originated by
firmware and captured by their respective device drivers. These events reflect
warning, debugging, and/or informative messages for the end user. These
events are kept in a finite queue inside the kernel, awaiting extraction by user
space programs such as CLI and/or 3DM.
The /cx show alarms command displays all available alarms on a given
controller. The default is to display the most recent alarm or AEN message
first. The user can also use the [
reverse
] attribute to display the most recent
alarm or AEN message last.
Alarms generated on 7000/8000 controllers do not have dates, so you will see
a '-' in the Date column. This means that it is not applicable. In addition,
alarm messages on 7000/8000 controllers contain the severity in the message
text, so the Severity column also shows a '-'.
