On Mon, Nov 17, 2008 at 01:38:29PM -0600, Tim wrote: > > And this passage: > "If there is a broken or missing disk, we don't let you proceed without > explicit confirmation. The reason we do this is that once the storage pool > is configured, there is no way to add those disks to the pool without > changing the RAS and performance characteristics you specified during > configuration."
This is what I meant by "individual disks or arbitrarily populated JBODs" in my last message. We don't support addiing JBODs with broken or missing disks, but full (or half) populated JBODs can be added at will. > The post as a whole makes it unclear if you are able to add more disk in the > future or not without changing your RAS/performance. That specific example, > after re-reading, appears to be referring to the "one broken disk(s)". I > guess everything I've read about fishworks talks about "making your choice" > at first configuration, and doesn't really make it clear what the process or > requirements are for adding disk in the future. Knowing zfs, I made the > assumption that it was possible via means like you've described above. If I > had no exposure to zfs though, it might be a bit less clear, and I guess in > this case, I wasn't 100% positive even with the background I have. > > If I've missed something, it wouldn't be the first time ADD has gotten the > best of me, so I apologize. Feel free to correct as you see fit. I can update the blog entry if it's misleading. I assumed that it was implicit that the absence of the above (missing or broken disks) meant supported, but I admit that I did not state that explicitly, and not in the context of adding storage. Thanks, - Eric -- Eric Schrock, Fishworks http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
