I made snaplock compliance aggregate with ONTAP 9.1 ,and create volume in the compliance aggregate. Then I halted ONTAP to initialize all disks using boot menu No.4 , but it couldn't be initialized. All aggrigate including compliance aggregate is still remained. Root volume is initialized yet.
I'd like to know How the compliance aggregate disks are initialized , and is it possible to reuse them?
Disk 0b.00.10 is part of a SnapLock Compliance volume. It will not be overwritten or formatte Disk 0a.00.9 is part of a SnapLock Compliance volume. It will not be overwritten or formatted
The document "Technical FAQ SnapLock ONTAP9.0 and 9.1" says
"When all the WORM data has expired in a SnapLock Compliance volume, the volume can be deleted." "SnapLock flexible volumes on an aggregate are deleted, the aggregate can also be delete"
Technical FAQ SnapLock ONTAP 9.0 and 9.1 Siddharth Agrawal, NetApp Version 1.1
Some volumes are still remaied on the disks and I can't delete them.
We make it very difficult to remove snaplock data - on purpose.
Assuming the system is not under support or in production, at this point I would suggest pulling the disks containing the aggr out of the system and zeroing them on a linux system (ensuring you use correct block sizes), and you should be able to re-use them after doing a zero spares. Never done it myself, but I know we check for a certain signature on the disks to determine if they are snaplock.
I tried zeroing disks on the server(IBM system x 3650) using erasing tool ,and it failed. All process of zeroing were finished with no-fatal errors ,but the following scsi error occured. --- * fail scsi Disk IBM ServerRAID MF5015 2.12 837GiB(898GB) 001709a72368e8c820d0251F04b ---
But this trouble was solved by other way. Compliance aggregate was deleted with following ontap command .