Robert Milkowski wrote:
Thumpers come with Solaris pre-installed and already configured one pool.
It's a collection of raid-z1 groups but some groups are smaller than the others.
I'll reconfigure it anyway but I'm just curious what side-effects can there be
with such a config?
Any performance hit? All space will be used?
Here is some of our thoughts which led to the decision to pre-configure
what you see on thumper.
1. Unallocated disk space doesn't exist. You will notice that all other
vendors who pre-install OSes on their systems ship with all of the space
allocated. For example, buy a Mac, do a df and all of the space can be
seen as allocated. Traditionally, Sun has delivered pre-installed systems
with unallocated space and if you wanted to use it, you had to search for
it, use format, etc.
2. It takes only one command to destroy the zpool. This fits with #1. I'm
a strong advocate for #1. It is easier to destroy the pre-installed zpool
and recreate it than to search for space using format (or whatever). This
is especially true for a large JBOD like thumper.
3. The data should be protected by default.
4. The available space should be maximized, given constraint #3. Big-wide
raidz1 sets are not a good idea, hence the multiple sets. Incidentally,
while it doesn't really make much difference, wrt data availability, which
controller you use, we knew that people would freak out if we didn't spread
the vdevs across the controllers.
5. We're not using a hot spare. This is a concession for #1. But if you
truly value data availability and retention, use a hot spare.
So, what you get, out of the box, is a large pool ready to be used. The pool
has respectable performance and data protection. But, if you need to configure
for more performance or data protection, then it is easy to do.
P.S. did you upgrade the OS? I'd consider the need for 'zpool upgrade' to be
a bug.
-- richard
# zpool status
pool: zpool1
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'. Once this is done, the
pool will no longer be accessible on older software versions.
scrub: scrub stopped with 0 errors on Thu Nov 2 09:29:14 2006
config:
NAME STATE READ WRITE CKSUM
zpool1 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t0d0 ONLINE 0 0 0
c1t0d0 ONLINE 0 0 0
c4t0d0 ONLINE 0 0 0
c6t0d0 ONLINE 0 0 0
c7t0d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t1d0 ONLINE 0 0 0
c1t1d0 ONLINE 0 0 0
c4t1d0 ONLINE 0 0 0
c5t1d0 ONLINE 0 0 0
c6t1d0 ONLINE 0 0 0
c7t1d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t2d0 ONLINE 0 0 0
c1t2d0 ONLINE 0 0 0
c4t2d0 ONLINE 0 0 0
c5t2d0 ONLINE 0 0 0
c6t2d0 ONLINE 0 0 0
c7t2d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t3d0 ONLINE 0 0 0
c1t3d0 ONLINE 0 0 0
c4t3d0 ONLINE 0 0 0
c5t3d0 ONLINE 0 0 0
c6t3d0 ONLINE 0 0 0
c7t3d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t4d0 ONLINE 0 0 0
c1t4d0 ONLINE 0 0 0
c4t4d0 ONLINE 0 0 0
c6t4d0 ONLINE 0 0 0
c7t4d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t5d0 ONLINE 0 0 0
c1t5d0 ONLINE 0 0 0
c4t5d0 ONLINE 0 0 0
c5t5d0 ONLINE 0 0 0
c6t5d0 ONLINE 0 0 0
c7t5d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t6d0 ONLINE 0 0 0
c1t6d0 ONLINE 0 0 0
c4t6d0 ONLINE 0 0 0
c5t6d0 ONLINE 0 0 0
c6t6d0 ONLINE 0 0 0
c7t6d0 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c0t7d0 ONLINE 0 0 0
c1t7d0 ONLINE 0 0 0
c4t7d0 ONLINE 0 0 0
c5t7d0 ONLINE 0 0 0
c6t7d0 ONLINE 0 0 0
c7t7d0 ONLINE 0 0 0
errors: No known data errors
bash-3.00#
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
