As far as I understand btrfs stores all data in huge chunks that are
striped, mirrored or "raid5/6'ed" throughout all the disks added to the
filesystem/volume.
How does btrfs deal with different sized disks? let's say that you for
example have 10 different disks that are 100GB,200GB,300GB...1000GB and
you create a btrfs filesystem with all the disks. How will the raid5
implementation distribute chunks in such a setup. I assume the
stripe+stripe+parity are separate chunks that are placed on separate
disks but how does btrfs select the best disk to store a chunk on? In
short will a slow disk slow down the entire "array", parts of it or will
btrfs attempt to use the fastest disks first?
Also since btrfs checksums both data and metadata I am thinking that at
least the raid6 implementation perhaps can (try to) reconstruct corrupt
data (and try to rewrite it) before reading an alternate copy. Can
someone please fill me in on the details here?
Finaly how does btrfs deals with advanced format (4k sectors) drives
when the entire drive (and not a partition) is used to build a btrfs
filesystem. Is proper alignment achieved?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
