ozan s. yigit wrote:
we thought we would try adding a disk to an existing raidz pool
named backup:
# zpool status
...
NAME STATE READ WRITE CKSUM
backup ONLINE 0 0 0
raidz ONLINE 0 0 0
c4t2d0 ONLINE 0 0 0
...
c4t2d5 ONLINE 0 0 0
add the next disk, we need a bit more space:
# zpool add backup c4t2d6
# zpool status
...
NAME STATE READ WRITE CKSUM
backup ONLINE 0 0 0
raidz ONLINE 0 0 0
c4t2d0 ONLINE 0 0 0
...
c4t2d6 ONLINE 0 0 0
ah. looks like the new disk is not a part of the raidz set,
yet the diskspace in the pool increased appropriately. if this
pool is used as is, can it still offer the raidz guarantee?
only for the bits that happen to fall into the raidz set but
not the additional disk?
i am confused about the overall failure characteristics of such
a setup. [maybe it is a boneheaded thing to do, but one gets no
warning from zpool if it is...]
What bits are you running?
I don't think this has changed since ZFS integrated but on recent nevada
bits you do get an error:
thumper-12tb# zpool create -f backup raidz c1t0d0 c1t1d0 c1t2d0 c1t3d0
thumper-12tb# zpool status
pool: backup
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
backup ONLINE 0 0 0
raidz1 ONLINE 0 0 0
c1t0d0 ONLINE 0 0 0
c1t1d0 ONLINE 0 0 0
c1t2d0 ONLINE 0 0 0
c1t3d0 ONLINE 0 0 0
errors: No known data errors
thumper-12tb# zpool add backup c7t7d0
invalid vdev specification
use '-f' to override the following errors:
mismatched replication level: pool uses raidz and new vdev is disk
thumper-12tb# uname -a
SunOS thumper-12tb 5.11 onnv-gate:2006-10-23 i86pc i386 i86pc
thumper-12tb#
Did you use the -f flag when you added the single disk vdev?
eric
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
