Query Not Zeroed disks

[SEENIKANNAN]

Hi,

After destroying the aggr we could see disks will be part of spare disks with not zeroed.

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
Spare disks for block checksum
spare v5.25 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)
spare v5.26 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)
spare v5.27 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448 (not zeroed)
spare v5.28 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448
spare v5.29 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448
spare v5.32 v5 ? ? FC:B 0 FCAL 15000 1020/2089984 1027/2104448

Questions is why disks are showing as not zeroed?

Was there any information available on the destroyed aggr?

Regards,

SEENIKANNAN

[GrumpyOldMen · Accepted solution]

I guess that, when you destroy an aggregate, the data that is still there is not really erased but made unavailable for access.  When you really want that the disks do not contain any data when the storage is end of use, you have to sanitize disks....

Spare disks can be added to an aggregate, can be used for creating a new one.... But in all cases the disks must contain only zeros. Adding zeros does not affect parity calculation. So that way we can hot-add disks,that's why zeroing is needed.