The IBM ESS F20 / 800 would format the DDM when creating raid groups or deleting raid groups and volumes. With a dynamic allocation of space to a track, you must wait until the device is empty, then erase the whole array several time to go through the entire backing space.
On Wed, Dec 12, 2012 at 10:59 PM, Don Williams <[email protected]> wrote: > I mostly agree. I've been in shops with 10+ year old DASD, so they might > still customers using structured log file DASD. You need to how your DASD > works, in order to develop a reliable erasure plan. > > However, I had a teammate delete the virtual volumes on old shark prior to > erasing the data. Would simply reallocating the volumes (assuming it would > put them back in the same spot) and erasing them, reliably remove all of the > data? I'm not smart enough to know for sure. Then you have to know how the > DASD handles bad tracks/sectors. There could be residual data in bad > tracks/sectors that have been replaced. How do you erase the no longer used > bad tracks? I know that most DASD has spare sectors on each track, so erasing > the track probably erases the bad sectors as well. But I'm not smart enough > to know for sure. > > Whether or not you consult an expert depends on how sure you need to be that > the every last bit of your data has been completely and throughly erased or > made unreadable. > <deleted> -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
