> If the user knew that they > intend to format a disk with potentially unsafe data on it they could just > bring > it online unformatted. (By unsafe I mean data that may be partially in a good > format and partially in bad).
Or you could configure your directory manager to erase on deallocate (out of the box code that is fully supported by CA support and doesn't require a user-written extension to the directory manager code) and you won't have this problem in the first place. I guess I'm kinda with Mark here: the existence of this problem is a process issue, not a technical one. This is a case where (in Everything You Need To Know In Life You Learn in Kindergarten terms) you need to start with washing your toys in the sink if they're dirty and carefully put away your toys and clean up after yourself when you're done playing. You need to follow good practices when adding and deleting disks from your system (ie do a clean CPVOL FORMAT when adding a volume to the system disk pools from another place) and always erase space when you release it. Then your system will start tidy and stay that way. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
