WARNING:During execution of the command,
PowerFlex checks that the device is clear before adding it. If the device is not clear, an error message is returned, and the command fails for that device. If you would like to overwrite existing data on the device by forcing the command, use the
force_device_takeover flag. Note that this flag destroys all existing data on the device!
Full path of the device to be added. A device can be a disk, an unmounted partition, or a file that represents free space on a mounted device.
--device_name
<NAME>
Name to assign to the device
--storage_pool_name
<NAME>
Storage Pool name
--storage_pool_id
<ID>
Storage Pool ID
--acceleration_pool_name
<NAME>
Acceleration Pool name
--acceleration_pool_id
<ID>
Acceleration Pool ID
--force_device_takeover
Add the device, ignoring data from other SDSs on the device.
WARNING:Use this flag with caution, because all data on the device will be destroyed.
--media_type {HDD |
SSD}
Media type of the device, where the device will be HDD or SSD.
--external_acceleration
<TYPE>
External acceleration for the device where
<TYPE> can be one of the following:
none
The device is not accelerated by non-PowerFlex cache.
read
The device is accelerated by a non-PowerFlex read cache.
write
The device is accelerated by a non-PowerFlex write cache.
read_and_write
The device is accelerated by both non-PowerFlex read and write cache.
--test_time
<TIME>
The maximum test run-time in seconds. Default: 10. The test will stop when it reaches either this limit, or the time it takes to complete 128 MB of data read/write, whichever is first. When
no_test is selected, this switch is ignored.
Test options (choose one):
By default,
PowerFlex tests the performance of the device being added before its capacity can be used, and saves the results. Two tests are performed: random writes and random reads. When the tests are complete, the device capacity is added automatically to the Storage Pool used by the MDM. To modify this behavior, specify one of the test options:
--test_only
Devices will be tested, but not used. To start using their capacity, run the
--activate_sds_device command.
--no_test
The device capacity will be used without any device testing.
<BLANK>
Read and write test will be run on devices before their capacity is used.
The following devices are considered to be not "clear," and thus cannot be added to an SDS:
Linux: A complete device with either a file system or partition, or a partitioned device with a file system.
Windows: A complete device with a partition, or a partitioned device with a file system.
ESX: Same as the above, depending on the operating system of the SVM where the SDS is installed.
Limitations:
SAN devices will not be prevented from being added to an SDS.
Devices in an LVM group cannot be added to an SDS.
Within the database devices, only Oracle ASM devices can be detected and blocked.
SDS device names
Assigning each SDS device a meaningful name facilitates future object identification, because the defined name remains constant even if the path changes. When a name has not been defined, the system may display default system-defined names that use the SDS’s first IP address.
Each name should conform to the following rules:
Contains fewer than 32 characters
Contains only alphanumeric and punctuation characters
Is unique within the object type
NOTE:PowerFlex objects are assigned a unique ID that can be used to identify the object in CLI commands. You can retrieve the ID via a query or through the object’s property sheet in the
PowerFlex GUI.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\