[Eric Schrock:]
| Look at alternate cachefiles ('zpool set cachefile', 'zpool import -c
| <cachefile>', etc). This avoids scanning all devices in the system
| and instead takes the config from the cachefile.
This sounds great.
Is there any information on when this change will make it to Solaris?
(In particular, is it going to be in S10 update 6, or only in a later
version?)
[Rich Teer:]
| How many pools is "a bunch"? The ideal number of pools per server
| tends to one, so reducing the number of pools might be your best
| option.
At a guess, we will probably have on the order of fifty to seventy
pools per fileserver (each of them using at least two LUNs, and we
will have multiple fileservers, all of which can see all of the LUNs).
We want to use many pools because we feel that using many pools is a
simpler way to manage selling fixed-size chunks of storage to users than
putting them all in a few pools and using quotas.
(There are other situations that call for many pools; the example I
remember from an earlier discussion on zfs-discuss is someone who
expected to have a bunch of zones and wanted to be able to move each of
them between machines.)
- cks
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
