Lines Matching refs:drive
130 * If a drive goes up or down this could be returned as event type "change".
131 * The application could get the drive information to see that the "status"
134 * return events for all drive related changes, events will not necessarily be
141 * In general the API means "the parent node of the drive in the device tree"
143 * the drive controller depending on the type of the drive.
151 * mpxio. With mpxio the drive will have a unique name and a single controller
152 * (scsi_vhci). The physical controllers, the paths to the drive, can be
153 * obtained by calling dm_get_associated_descriptors with a drive descriptor and
155 * possibly some future similar feature, is controlling the drive.
157 * Without mpxio the drive does not have a unique public name (in all cases the
158 * alias(es) of the drive can be determined by calling
163 * a drive with two paths has the aliases c5t3d2 and c7t1d0. There will be two
167 * In the multi-path, non-mpxio case the drive has more than one alias.
168 * Although most of the drive attributes are represented on the drive (see
170 * aliases for the drive. Use dm_get_associated_descriptors to get the DM_ALIAS
173 * it can be used to get the target/lun for a SCSI drive with a single path.
221 * bus --- controller --- drive --- media |
236 * There could be additional types added to these enumerations as new drive and
282 * to get for the descriptor. The following enums specify the drive and slice
285 /* drive stat name */
306 /* drive */
443 void dm_get_slices(char *drive, dm_descriptor_t **slices,