On Fri, Oct 19, 2007 at 02:43:20PM -0400, Bill Sommerfeld wrote: > > so, the implication I get from the proposal is that > > zpool import -c <file> > > like > > zpool import > > merely reports on what's out there and importable but doesn't actually > open the pools, and you'd have to do something like: > > zpool import -c foo-cache foo-pool > > to actually import the pool. > > Is that correct? if so, that answers my question; hardening the former > case against toxic crud seems a lot easier than hardening the latter... >
Sort of. The '-c' option only changes the source of the configuration. The rest of the import command behaves in the same manner. We still do a ZPOOL_IOC_TRYIMPORT to read the true MOS config as well as determine vdev state, so we call spa_load() in either case. This is required to correctly determine whether the pool is importable or not. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
