On Mon, Feb 26, 2007 at 12:06:14PM -0600, Nicolas Williams wrote: > On Mon, Feb 26, 2007 at 10:05:08AM -0800, Eric Schrock wrote: > > The slow part of zpool import is actually discovering the pool > > configuration. This involves examining every device on the system (or > > every device within a 'import -d' directory) and seeing if it has any > > labels. Internally, the import action itself shoudl be quite fast, and > > is essentially the same speed as opening a pool normally. So the > > scalability is really depending on the number of devices in the system, > > not the number of devices within a pool. > > Couldn't all that tasting be done in parallel?
Yep, that's certainly possible. Sounds like a perfect feature for someone in the community to work on :-) Simply take zpool_find_import(), add some worker thread/pool model, and there you go. - Ericd -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
