This is tangential, but then arc review is all about feature
interaction.
1) What happens if the hotplugged replacement device is too small?
2) What's the interaction between autoreplace and automatic vdev growth
(when the underlying device gets bigger)?
Since we can't yet shrink a pool, i'm wondering if there aren't some
gotchas if someone plugs in a disk that's too big; they might not be
able to go back and replace it with one of the intended size.
Consider the following comedy of operational errors:
we start with a pool which looks like:
mirror
small1
small2
mirror
large1
large2
spare
large3
"small1" fails, and hot sparing kicks in to replace it with "large3".
resilvering is complete.
case #1: operator mistakenly pulls small2 instead of small1
does mirror #1 (reduced to a single functioning replica) autogrow to
size "large"?
case #2: operator pulls small1, and by mistake plugs in "large4" instead
of "small3". before noticing this error, "small2" fails.
.. or other variants of the above.
- Bill
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
