Wow, this forum is great and uber-fast in response, appreciate the responses,
makes sense.
Only, what does ZFS do to write to data? Let's say that you want to write x
blocks somewhere, is ZFS going to find a pointer to the space map of some
metaslab and then write there? Is it going to find a
1. Is it true that because block sizes vary (in powers of 2 of course) on each
write that there will be very little internal fragmentation?
2. I came upon this statement in a forum post:
[i]"ZFS uses 128K data blocks by default whereas other filesystems typically
use 4K or 8K blocks. This natur
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
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
/products/motherboard/Core2Duo/X48/C2SBX+.cfm
Gigabyte GA-X48-DS4
gigabyte:
http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2810
Intel S3200SHV
http://www.intel.com/Products/Server/Motherboards/Entry-S3200SH/Entry-S3200SH-overview.htm
Thanks for any help,
-Ilya
