Read me

service on a system that has native RAID utilities or RAID
utilities provided by vendors is not supported.
* The Storage Management service enables you to perform storage
tasks that are data-destructive. The Storage Management service
should be used by experienced storage administrators who are
familiar with their storage environment.
*****************************************************************************
***
Fixed Issues/defects
*****************************************************************************
***
Not Applicable.
*****************************************************************************
***
Known issues and Workarounds
*****************************************************************************
***
The following sections describe known problems associated with
Storage Management or the supported controllers.
* If a CacheCade drive is imported as part of a foreign configuration,
verify the state of the drive as it may have been imported as a
‘regular’ RAID 0 volume and not a CacheCade drive.
CacheCade will need to be reconfigured.
* Dell OpenManage Server Administrator Storage Management 3.3
does not support PERC 4 controllers and earlier versions
on VMware ESX4.x/ESXi 4.x and all 64-bit
Linux Operating Systems.
* Hot removal of enclosure is not supported in Storage Management.
It may result in unpredictable errors, such as stopping Storage
Management service.
* Creating many sliced span virtual disks using the spun-down drives
in the command line or GUI may result in unexpected result.
Workaround: After creating one sliced span virtual disk, wait
for some time to create the next sliced span virtual disk.
* In ESX4 Classic, 'deprecated SCSI ioctl' message is displayed on
the console
Problem: In VMware ESX 4.0 Classic system, the following
warning message(s) is displayed on the console:
“Program dsm_sa_datamgrd is using the deprecated SCSI ioctl,
Please convert it to SG_IO.” This is a kernel warning message
displayed when storage operations are in progress.
This is only a deprecation warning and not an indication
of a failing operation.
Workaround: Reduce the kernel logging level.