Disk auto replacement starts at the partner node after assigning internal spare disk

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 130

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: hw

Last Updated:

Applies to

ONTAP 9
FAS2820
FAS2720
FAS2750
Data aggregates using shared disks from the internal and the external shelf
raid.lm.disk.copyback.enable set to on

Issue

After replacing faulty disk at node02, assign the partition disk to node02 spare pool, but P1 partition auto-assign to node01 and start to replace the 02.7P1 data disk.

Thu Aug 07 10:57:30 +0900 [node02: dmgr_thread: raid.disk.inserted:info]: Disk 0b.00.2 Shelf 0 Bay 2 [NETAPP   X336_SCBPE04TA07 NA01] S/N [xxxxxxx] UID [5000C500:F9093037:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] has been inserted into the system

Thu Aug 07 11:09:42 +0900 [node02: sanown_io: diskown_changingOwner_1:notice]: params: {'diskname': '0b.00.2P1','oldownername': 'unowned', 'newownername': 'node02'}

Thu Aug 07 11:10:02 +0900 [node02: sanown_io: diskown_changingOwner_1:notice]: params: {'diskname': '0b.00.2P2','oldownername': 'unowned', 'newownername': 'node02' }

Thu Aug 07 11:10:52 +0900 [node02 sanown_io: diskown_changingOwner_1:notice]: params: {'diskname': '0b.00.2P1','oldownername': 'node02', 'newownername': 'node01', }

Thu Aug 07 11:11:03 +0900 [node01: config_thread: raid.rg.diskcopy.start:notice]: /Cluster01_01_NL_SAS_1/plex0/rg0: starting disk copy from 0b.02.7P1 (S/N [xxxxxxx]) to 0b.00.2P1 (S/N [xxxxxxx]). Reason: Disk replace was started..

No disk replace event occur between 00.2 and 02.7 ever.