Lines Matching refs:drive
86 disks the device names will not change in the event of a disk drive failure.
238 there are only at most 6 usable partitions on each logical drive, systems
239 requiring more partitions should subdivide a drive group into multiple logical
243 will cause the logical drive geometry to have more than 65535 cylinders which
282 soon as a drive replacement is made available.
365 The "kill" command marks the physical drive <channel>:<target-id> as DEAD.
371 The "make-online" command changes the physical drive <channel>:<target-id>
374 one of them back online, after which a rebuild to the final drive is
377 Warning: make-online should only be used on a dead physical drive that is
378 an active part of a drive group, never on a standby drive. The command
379 should never be used on a dead drive that is part of a critical logical
380 drive; rebuild should be used if only a single drive is dead.
384 The "make-standby" command changes physical drive <channel>:<target-id>
386 a dead drive was replaced after an automatic rebuild was performed onto a
387 standby drive. It cannot be used to add a standby drive to the controller
393 The "rebuild" command initiates an asynchronous rebuild onto physical drive
394 <channel>:<target-id>. It should only be used when a dead drive has been
397 check-consistency <logical-drive-number>
400 of <logical-drive-number> with automatic restoration. It can be used
416 DAC960PJ controller. The physical drives are configured into a single drive
417 group without a standby drive, and the drive group has been configured into two
451 1:1 is now disconnected, simulating a drive failure. The failure is noted by
466 from /proc/rd also reflects the drive failure. The status message in
489 the logical drives in a performance degraded mode until the failed drive is
492 functioning drive, or if the physical drive was killed without having failed
494 controller to initiate a rebuild operation onto the newly replaced drive:
588 DAC960PJ controller. The physical drives are configured into a single drive
589 group with a standby drive, and the drive group has been configured into two
623 1:2 is now disconnected, simulating a drive failure. The failure is noted by
635 Since a standby drive is configured, the controller automatically begins
636 rebuilding onto the standby drive:
642 reflects the drive failure and automatic rebuild. The status message in
724 Note that the absence of a viable standby drive does not create an "ALERT"
726 told that this has occurred and that the newly replaced drive should become the
727 new standby drive:
734 standby drive, and the status message that results from the operation is then