Have you tried the disk sanitize command? I haven't tried this, but the man page seems to talk about what you want to do. Let us know if this works for you.

The disk sanitize start, disk sanitize abort, and disk sanitize status commands are used to start, abort, and obtain status of the disk sanitization process. This pro- cess runs in the background and sanitizes the disk by writing the entire disk with each of the defined pat- terns. The set of all pattern writes defines a cycle; both pattern and cycle count parameters can be specified by the user. Depending on the capacity of the disk and the number of patterns and cycles defined, this process can take several hours to complete. When the process has com- pleted, the disk is in the sanitized state. The disk sani- tize release command allows the user to return a sanitized disk to the spare pool. -G On 10/22/07, Stefan Funke bundy@arcor-online.net wrote:

Andrew Siegel wrote:

...

In my opinion (as a 12-year customer), the 16TB limit is the number one deficiency in NetApp software at the moment, and perhaps their biggest deficiency ever. I would be very surprised if they weren't losing customers over this issue.

Acknowledged. I think they changed the limit from 10TB to 16TB with Ontap7, correct? Disc sizes are growing and growing - unless NetApp changes to solid state disks (flash), a higher limit would be nice to have.

BTW, I'm searching for a way to securely wipe out all data at our R200 disks. (ATA, 154x274gig) I wanted to build a big volume, but the 16TB hit me too. Has anyone ever played with 'dd' at Ontap side? Is there a hidden random device (/dev/random) I can use to create random data? Any hints? :)