I like the link you sent along... They did a nice job with that.
(but it does show that mixing and matching vastly different drive-sizes
is not exactly optimal...)
http://www.drobo.com/drobolator/index.html
Doing something like this for ZFS allowing people to create pools by
mixing/matching drives, raid1, and raidz/z2 drives in a zpool makes for
a pretty cool page. If one of the statistical gurus can add MTBF
MTTdataLoss etc. to that as a calculator at the bottom that would be
even better. (someone did some static graphs for different thumper
configurations for this in the past... This would just make that more
general purpose/GUI driven... Sounds like a cool project)
--
No mention anywhere of "removing drives" thereby reducing capacity
though... Raid-re-striping isn't all that much fun, especially with
larger drives... (and even ZFS lacks some features in this area for now)
See the answer to you other question below. (from their FAQ)
-- MikeE
What file systems does drobo support?
RESOLUTION:
Drobo is a usb external disk array that is formatted by the host
operating system (Windows or OS X). We currently support NTFS, HFS+, and
FAT32 file systems with firmware revision 1.0.2.
Drobo is not a ZFS file system.
STATUS:
Current specification 1.0.2
Applies to:
Drobo DRO4D-U
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Hull
Sent: Saturday, May 24, 2008 7:00 PM
To: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] ZFS: A general question
OK so in my (admittedly basic) understanding of raidz and raidz2, these
technologies are very similar to raid5 and raid6. BUT if you set up one
disk as a raidz vdev, you (obviously) can't maintain data after a disk
failure, but you are protected against data corruption that is NOT a
result of disk failure. Right?
So is there a resource somewhere that I could look at that clearly
spells out how many disks I could have vs. how much resulting space I
would have that would still protect me against disk failure (a la the
"Drobolator" http://www.drobo.com/drobolator/index.html)? I mean, if I
have a raidz vdev with one disk, then I add a disk, am I protected from
disk failure? Is it the case that I need to have disks in groups of 4
to maintain protection against single disk failure with raidz and in
groups of 5 for raidz2? It gets even more confusing if I wanted to add
disks of varying sizes...
And you said I could add a disk (or disks) to a mirror -- can I force
add a disk (or disks) to a raidz or raidz2? Without destroying and
rebuilding as I read would be required somewhere else?
And if I create a zpool and add various single disks to it (without
creating raidz/mirror/etc), is it the case that the zpool is essentially
functioning like spanning raid? Ie, no protection at all??
Please either point me to an existing resource that spells this out a
little clearer or give me a little more explanation around it.
And... do you think that the Drobo (www.drobo.com) product is
essentially just a box with OpenSolaris and ZFS on it?
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
