The new TD appropriately reports in_use data (as it's reported by libdiskmgt) for disk slices. The new TI, however, does not cross reference the in_use data prior to instantiating a target primarily because TI is supposed to be dumb.
Instead, it is proposed that the add_slice/delete_slice API call be made smarter about honoring the in_use data. So, for example - - If a given slice is in use (by say zfs) and add_slice() is called with the same slice, an error would be communicated via the errorsvc - If a given slice is in use and delete_slice() is called with the same slice, an error would be communicated via the errorsvc The caller of the API would see this error and either choose to ignore it or take corrective action as the case may be. Does this seem adequate to the consumers of TI/TD? Thanks, Alok _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
