Kjetil Torgrim Homme writes:
> Cindy Swearingen writes:
>> You might check the slides on this page:
>>
>> http://hub.opensolaris.org/bin/view/Community+Group+zfs/docs
>>
>> Particularly, slides 14-18.
>>
>> In this case, graphic illustrations are probably the best way
>> to answer your questions.
So then of what use is the parity?
And how is the metadata used to reconstruct bad data? I understand obviously
what the metadata contains but I don't get how ZFS traverses through a file
system and USES the metadata to construct bad blocks.
I understand that you write everything to separate b
On Thu, Nov 05, 2009 at 11:55:58AM -0800, Ilya wrote:
> Slide 18 shows variably sizes extents but doesn't explain the process
> of full-on write. What I'm looking for is one example. I still don't
> understand how it works with variable sized extents. So if you have 2
> stripe units on one disk an
Hey
Thanks for the slides but some things are still unclear.
Slide 18 shows variably sizes extents but doesn't explain the process of
full-on write. What I'm looking for is one example. I still don't understand
how it works with variable sized extents. So if you have 2 stripe units on one
disk
Forgot to add, are those four stripe units (for that one file) above considered
the stripe itself? Or are each of those stripe units on the seperate disks
considered as separate stripes?
--
This message posted from opensolaris.org
___
zfs-discuss maili
Researching about ZFS and had a question leating to Raid-Z and the striping.
So, I was glacing over Jeff's blog (http://blogs.sun.com/bonwick/entry/raid_z):
[i]"RAID-Z is a data/parity scheme like RAID-5, but it uses dynamic stripe
width. Every block is its own RAID-Z stripe, regardless of block
