Hi Darren, thank you very much for your help. Please see my comments below.
Jan Darren J Moffat wrote: > jan damborsky wrote: >> Hi John, >> >> I like this idea - it would be clear solution for the problem. >> Is it possible to manage custom parameters with standard CLI >> commands (these are used by the installer for manipulating ZFS >> entities) - zpool(1M), zfs(1M), ... ? >> >> I am asking, since I haven't found information about setting >> custom parameters neither in man pages nor in >> "Solaris ZFS Administration Guide" available on opensolaris.org, >> I have probably missed it. > > As of snv_96 pool's don't have user properties otherwise you would > be able to do this: > > zpool set caiman:install=preparing rpool > .... > zpool set caiman:install=ready rpool > ... > zpool set caiman:install=complete rpool > > You can set user properties on a dataset so you could do this: > > zfs set caiman:install=preparing rpool/ROOT That sounds reasonable. It is not atomic operation from installer point of view, but the time window is really short (installer can set ZFS user property almost immediately after pool is created). As far as pools imported manually by user are concerned, is there anything installer could do about this before 6733239 is fixed ? I mean, if user imports "rpool" (e.g. from another disk) which contains valid installation of Solaris, installer can't proceed with installation, since it can't export the pool in order to release the "rpool" name for its own purposes (when exported, pool can't be booted anymore). > > And log an RFE for having user defined properties at the pool (if one > doesn't already exist). I will go through the existing issues and will file new RFE for this if one doesn't exists. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
