jasun's blog

Populating the VTOC

# cat wipe

for i in /dev/rdsk/c[!0]*s2
do
fmthard -s /dev/null $i
done
#

An easy way to destroy data on all disks that are not on controller 0. I just destroyed our array, on purpose of course. So now, I can re-create a new array and learn in the process.

One of the benefits of having labs to play with on courses or in general.
Below is a before / after status, after running the wipe script above.

Before:

# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced - - online
c6t0d0s2 sliced - - online
c6t1d0s2 sliced - - online
c6t2d0s2 sliced - - online
c6t4d0s2 sliced - - online
c6t5d0s2 sliced - - online
c6t6d0s2 sliced - - online
c6t16d0s2 sliced - - online
c6t17d0s2 sliced - - online
c6t18d0s2 sliced - - online
c6t19d0s2 sliced - - online
c6t20d0s2 sliced - - online
c6t21d0s2 sliced - - online
c6t22d0s2 sliced - - online

After:

# wipe
# vxdctl enable (re-scan drives in Veritas)
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced - - online
c6t0d0s2 sliced - - error
c6t1d0s2 sliced - - error
c6t2d0s2 sliced - - error
c6t4d0s2 sliced - - error
c6t5d0s2 sliced - - error
c6t6d0s2 sliced - - error
c6t16d0s2 sliced - - error
c6t17d0s2 sliced - - error
c6t18d0s2 sliced - - error
c6t19d0s2 sliced - - error
c6t20d0s2 sliced - - error
c6t21d0s2 sliced - - error
c6t22d0s2 sliced - - error

#

The 2 drives on controller 0 are still active because we wanted those to be left alone, because they are the boot disk and another disk in the machine. All of the other drives are in the array. We could have messed the box up as well, as it could have had a jump start.