>No one has said that you can't increase the size of a zpool. What can't
>be increased is the size of a RAID-Z vdev (except by increasing the size
>of all of the components of the RAID-Z). You have created additional
>RAID-Z vdevs and added them to the pool.
If following is nonsense, please bear with me being a newbie...
Suppose you partition the each of the n disk into m equally sized partitions,
make m raidz vdevs and finally create one pool from them all. When you then
wish to add another disk, you first partition it as the previous ones, then
for i in 1:m {
remove raidz vdev number i from the pool
destroy raidz vdev number i
create a raidz vdev from partition i of each of the n+1 disks
add the new raidz vdev to the pool
}
This would demand that 1/m:th of the available disk space would be free, but
would make it possible to add additional disks without backup/restore the
entire data. Also, it would make it possible to add disks of different sizes,
since some raidz:s could include partitions from more disks than others.
The interesting question is, what would the performance hit be for pooling m
raidz:s from partitions instead of using one regular raidz? Does the driver in
some way collect requests for the same disk, which would be destroyed when
multiple vdevs in the same pool come from the same disk?
Cheers
Anders
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
