Hi
This is great. How does the current code handle corruption on a drive,
or two drives with RAID-6 in a stripe? Is the checksumming done per
drive or for the whole stripe?
roy
On 6. aug.. 2009, at 12.17, David Woodhouse wrote:
If we've abandoned the idea of putting the number of redundant blocks
into the top bits of the type bitmask (and I hope we have), then we're
fairly much there. Current code is at:
git://, http://git.infradead.org/users/dwmw2/btrfs-raid56.git
git://, http://git.infradead.org/users/dwmw2/btrfs-progs-raid56.git
We have recovery working, as well as both full-stripe writes and a
temporary hack to allow smaller writes to work (with the 'write hole'
problem, of course). The main thing we need to do is ensure that we
_always_ do full-stripe writes, and then we can ditch the partial
write
support.
I want to do a few other things, but AFAICT none of that needs to
delay
the merge:
- Better rebuild support -- if we lose a disk and add a replacement,
we want to recreate only the contents of that disk, rather than
allocating a new chunk elsewhere and then rewriting _everything_.
- Support for more than 2 redundant blocks per stripe (RAID[789] or
RAID6[³⁴⁵] or whatever we'll call it).
- RAID[56789]0 support.
- Clean up the discard support to do the right thing.
--
David Woodhouse Open Source Technology
Centre
David.Woodhouse@xxxxxxxxx Intel
Corporation
--
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
--
Roy Sigurd Karlsbakk
(+47) 97542685
roy@xxxxxxxxxxxxx
http://blogg.karlsbakk.net/
--
I all pedagogikk er det essensielt at pensum presenteres
intelligibelt. Det er et elementært imperativ for alle pedagoger å
unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de
fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
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
