Spare drive auto-partitioned with spare_low condition for container
Applies to
- MCC IP
- RAID groups with partitioned and not partitioned drives
- Same container size for the drives in those RAID groups
- System with a dedicated CORE dump device.
- Systems running fixed version for bug 1489180 (Auto-partition of disks post initialization on IP MetroCluster configuration might cause low spares condition)
Issue
- No spares drives available for the RAID groups with unpartitioned drives
- A manual drive un-partitioning is automatically reverted by ONTAP (the drive is auto-partitioned again immediately)
- Spare drives automatically partitioned for the RAID groups with partitioned disks.
RAID-LM.log
example:
01-01-2023 00:00:02: 1.1.1 is an SSD that needs to be partitioned post init.
01-01-2023 00:00:05: ksmfRaidLmPartitionDiskAssign: _RAID_LM : 0a.01.1 request received.
01-01-2023 00:00:05: sanown-assign -owner node_name-02 -pool 0 -disk 0a.01.1P1: succeeded
01-01-2023 00:00:05: sanown-assign -owner node_name-01 -pool 0 -disk 0a.01.1P2: succeeded
01-01-2023 00:00:05: sanown-assign -owner node_name-01 -pool 0 -disk 0a.01.1P3: succeeded
01-01-2023 00:00:06: ksmfPartitionDiskCreate run -method partitionMethod_t_root_data1_data2 -pool-uuid ... -assign-partitions true -disk 0a.01.1 -reason RAID_LM: succeeded