> Perhaps I'm not asking my question clearly. I've already experimented > a fair amount with zfs, including creating and destroying a number of > pools with and without redundancy, replacing vdevs, etc. Maybe asking > by example will clarify what I'm looking for or where I've missed the > boat. The key is that I want a grow-as-you-go heterogenous set of > disks in my pool:
> Let's say I start with a 40g drive and a 60g drive. I create a > non-redundant pool (which will be 100g). At some later point, I run > across an unused 30g drive, which I add to the pool. Now my pool is > 130g. At some point after that, the 40g drive fails, either by > producing read errors or my failing to spin up at all. What happens to > my pool? Since you have created a non-redundant pool (or more specifically, a pool with non-redundant members), the pool will fail. > The problem I've come across with using mirror or raidz for this setup > is that (as far as I know) you can't add disks to mirror/raidz groups, > and if you just add the disk to the pool, you end up in the same > situation as above (with more space but no redundancy). You can't add to an existing mirror, but you can add new mirrors (or raidz) items to the pool. If so, there's no loss of redundancy. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
