Make vol1 the root volume Offline & destroy vol0 after vol1 deemed okay!
A warning here. There's currently a bug in Ontap5.0R1 related to destroying a large volume. I had two volumes, vol0 (two disk root volume) and vol1 (22-disk data volume). I did a vol destroy on vol1.
The toaster then worked fine until the next reboot. Then it failed to reboot. I had to put in the floppy, and hit the "normal boot" option.
A "download" command made it so it booted successfully (until the next time I did a "vol destroy" on most of my disks).
So the warning is: until the bug is fixed, if you do a vol destroy on a large volume, run a "download" command after the "vol destroy" is complete, but before the next reboot.
---- Here's my theory as to the cause (translation: guess):
The netapp mirrors the OS on the header of all the disks.
At least half of the disks must have the same OS copy/version/checksum/magic-number in order for the netapp to boot correctly (guess #1)
The "vol destroy" uses a hardware-quick-erase feature which blows away the whole disk, not just the data portion. This blows away the OS portion of the disk.
Viola! After a vol destroy on 22 of my 24 disks, I now have a valid OS on less than half the disks. Non-floppy boots fail until I get it up with a floppy, and run download (but no data is lost).
----
This bug has been reported to Netapp, and they're working on it.
By the way, I've been favorably impressed with the reliability of Ontap-5.0 in my current benchmarking/testing project. Based on my observations (100% unix, no NT observations), I wouldn't hesitate to put it on my production servers at this time. The "vol destroy" on that many disks is a pretty abnormal operation for a production server---you just have to remember to run "download" until they patch it.
----
Darrell Root rootd@nas.nasa.gov