Jack, Good point. Read on. The use case here could be deployment of a computer that is slated for complete reinitialization and removal of any existing data.
In principle, the security for the disk is not provided in selection criteria, but in the partition, slice, and zfs pool creation. The design attempts to preserve data in all cases, unless specified otherwise. However, you have identified a case where the mirror is created without regard to what might be on the disk. I would propose that the default behavior should be to prevent creating of zpools and mirrors on "disks that have data", unless we offer an element to override that protection. "Disks that have data" must be more clearly described. Thanks for pointing this out, William Jack Schwartz wrote: > Hi William. > > On 05/26/09 07:01, William Schumann wrote: >> (snip) >> >> Example: install on boot disk, use some selected disk as raid2 >> mirror, and use another selected disk over 30GB for zfs pool newpool >> mounted at /export1 > Sounds dangerous to have the system pick an arbitrary disk based on > size. If we do this, we should check the disk label that the disk was > not used, to prevent accidential erasure. > > Thanks, > Jack
