THANK YOU VERY MUCH EVERYONE!!
You have been very helpful and my questions are (mostly) resolved. While I am
not (and probably will not become) a ZFS expert, I now at least feel confident
that I can accomplish what I want to do.
My last comment on this is this:
I realize that ZFS is designed
Will and several other people are correct.
I had forgotten that ZFS does a funky form of concatenation when you use
different size vdevs. I tend to ignore this case, because it's kinda
useless (I know, I know, there's people who use it, but, really...
)
Basically, it will stripe across vdevs as
> Thus, if you have a 2GB, a 3GB, and a 5GB device in a pool,
> the pool's capacity is 3 x 2GB = 6GB
If you put the three into one raidz vdev it will be 2+2
until you replace the 2G disk with a 5G at which point
it will be 3+3 and then when you replace the 3G with a 5G
it will be 5+5G. and if yo
On Sun, May 25, 2008 at 1:27 AM, Erik Trimble <[EMAIL PROTECTED]> wrote:
> If there are more than 1 vdev in a pool, the pool's capacity is
> determined by the smallest device. Thus, if you have a 2GB, a 3GB, and a
> 5GB device in a pool, the pool's capacity is 3 x 2GB = 6GB, as ZFS will
> only do f
Steve Hull wrote:
> Sooo... I've been reading a lot in various places. The conclusion I've
> drawn is this:
>
> I can create raidz vdevs in groups of 3 disks and add them to my zpool to be
> protected against 1 drive failure. This is the current status of "growing
> protected space" in raidz
Sooo... I've been reading a lot in various places. The conclusion I've drawn
is this:
I can create raidz vdevs in groups of 3 disks and add them to my zpool to be
protected against 1 drive failure. This is the current status of "growing
protected space" in raidz. Am I correct here?
Thi
ris.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 a
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 d
Hi Steve,
Am 24.05.2008 um 10:17 schrieb [EMAIL PROTECTED]:
> ZFS: A general question
> To: zfs-discuss@opensolaris.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=UTF-8
>
> Hello everyone,
>
> I'm new to ZFS and OpenSolaris, and I've been reading the docs on
> ZFS (the
> Anyway you can add mirrored, [...], raidz, or raidz2 arrays to the pool,
> right?
correct.
> add a disk or two to increase your protected storage capacity.
if its a protected vdev, like a mirror or raidz, sure... one can
force add a single disk, but then the pool isn't protected until
you a
On Sat, May 24, 2008 at 3:12 AM, Steve Hull <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> I'm new to ZFS and OpenSolaris, and I've been reading the docs on ZFS (the
> pdf "The Last Word on Filesystems" and wikipedia of course), and I'm trying
> to understand something.
>
> So ZFS is self-healin
Hello everyone,
I'm new to ZFS and OpenSolaris, and I've been reading the docs on ZFS (the pdf
"The Last Word on Filesystems" and wikipedia of course), and I'm trying to
understand something.
So ZFS is self-healing, correct? This is accomplished via parity and/or
metadata of some sort on the
12 matches
Mail list logo
