User guide

DataDirect Networks SFA™ OS 2.2.1.3 Release Notes Revision A1 | 9
NOTE: A controller will not attempt to shut down until it has completed the
flushing of its mirrored cached data which may take up to an hour
depending on I/O load and I/O transfer sizes.
• The drive serial number reported in SHOW PD output may contain additional
characters that are not on the disk label. The serial number on the disk label will
always be contained within the potentially more verbose string reported by SFA OS.
• The SS7000 enclosure does not support the SET SLOT xx POWER OFF command
with enclosure firmware versions prior to 05.02.01.
• In the SS7000, when removing an I/O module or cable under load, it is possible that
one or more disks could be marked failed which would change the redundancy of the
storage pools. This is due to in-flight I/O being timed out and retried before the IOC
reports the drive as missing. There is a high probability that the newly failed drives
are fine and can be returned to service by clearing the failed state and reassigning
them to pools.
Use the following procedure to clear a failed drive and reassign it back to a pool:
show unassigned failed
Shows which PDs have failed; get drive’s
<id>
show pool
Shows which pools are involved
clear pd <id> failed
<id> is from show unassigned output
assign pd <id> to pool-id set
Pool-ID is shown in the show pool output
NOTE: If the pool sparing policy is set to "SWAP", the SFA will typically auto
rebuild the drives, using fractional or full rebuild depending on the
duration of the interruption.
• If a drive is declared as Unknown or otherwise is missing from a pool and you choose
the GUI to spare a drive into the pool, the drive size may display as needing a drive of
0 GB size.
[DE14932]
• If stack commands (CLI commands starting with "app") are issued shortly after
rebooting a controller, you may encounter communication errors displayed in the
CLI, and failure of the attempted commands. Errors may include:
o Long delays followed by:
Communication connection failed for this command
o Or this message:
ASM initialization in progress
Suggested Work Around
o After the failed controller comes back up, do not immediately issue any CLI
commands besides "show controller".
o Connect to the remaining controller and issue this command:
$ show controller
o When "SHOW CONTROLLER" shows the remote controller in the output, focus
on the ULA field in the output. The remote controller will not show up until it
is fully booted.