Replying to a few folks in a digest format, because I'm lazy and don't
have that much to say.

On Wed, Sep 30, 2009 at 5:53 PM, Tim Cook <t...@cook.ms> wrote:
> What are you hoping to accomplish?  You're still going to need a drives
> worth of free space, and if you're so performance strapped that one drive
> makes the difference, you've got some bigger problems on your hands.

As I mentioned, the biggest win would be in a SOHO environment where
you may have bought more space than you need right now, and in the
meantime can use it for a wider stripe.

Don't think about it as a high performance filesystem, think about it
in the context of a Drobo-like device. It'll provide you with
protection from 2 drives failing (since it would require double
parity), or even better if there's free space available.

> BTW, you shouldn't need one disk per tray of 14 disks.  Unless you've got

We use one spare per shelf on our current NetApp hardware. No real
reason other than it makes the provisioning more consistent. Given the
large number of filers that we have, consistency is important.


On Wed, Sep 30, 2009 at 5:56 PM, Erik Trimble <erik.trim...@sun.com> wrote:
> What you describe makes no sense for single-parity vdevs, since it actually

I'm pretty sure I said that I wouldn't recommend it for anything less
than raidz2.

As far as gains? It would get you out of degraded mode, which can help
performance. This may not be important though, since I believe raidz2
with a single faulted device doesn't have much of an impact.


On Wed, Sep 30, 2009 at 6:01 PM, Matthew Ahrens <matthew.ahr...@sun.com> wrote:
> ability to move blocks around).  One minor downside to "hot space" would be
> that it couldn't be shared among multiple pools the way that hot spares can.

Why not? If you have the space available in the zpool, you should be
able to move the data to other vdevs and shrink the degraded one.
Unless bprewrite doesn't allow data to move between vdevs, that is.

-B

-- 
Brandon High : bh...@freaks.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to