RAID56

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(The history: The history isn't really helpful at this point.)
(Status: Not really "usable for most purposes" if a power failure is highly likely to cause corrupt data.)
Line 1: Line 1:
 
== Status ==
 
== Status ==
  
From 3.19, the recovery and rebuild code was integrated. This brings the implementation to the point where it should be usable for most purposes. Since this is new code, you should expect it to stabilize over the next couple of kernel releases.
+
From 3.19, the recovery and rebuild code was integrated. The one missing piece, from a reliability point of view, is that it is still vulnerable to the parity RAID "write hole", where a partial write as a result of a power failure will result in inconsistent parity data.
 
+
The one missing piece, from a reliability point of view, is that it is still vulnerable to the parity RAID "write hole", where a partial write as a result of a power failure may result in inconsistent parity data.
+
  
 
* Parity may be inconsistent after a crash (the "write hole")
 
* Parity may be inconsistent after a crash (the "write hole")
 +
* Parity data is not checksummed
 
* No support for discard? (possibly -- needs confirmation with cmason)
 
* No support for discard? (possibly -- needs confirmation with cmason)
 
* The algorithm uses as many devices as are available: No support for a fixed-width stripe (see note, below)
 
* The algorithm uses as many devices as are available: No support for a fixed-width stripe (see note, below)

Revision as of 11:17, 24 June 2016

Status

From 3.19, the recovery and rebuild code was integrated. The one missing piece, from a reliability point of view, is that it is still vulnerable to the parity RAID "write hole", where a partial write as a result of a power failure will result in inconsistent parity data.

  • Parity may be inconsistent after a crash (the "write hole")
  • Parity data is not checksummed
  • No support for discard? (possibly -- needs confirmation with cmason)
  • The algorithm uses as many devices as are available: No support for a fixed-width stripe (see note, below)

If you'd like to learn btrfs raid5/6 and rebuilds by example (based on kernel 3.14), you can look at Marc MERLIN's page about btrfs raid 5/6.

Note

Using as many devices as are available means that there will be a performance issue for filesystems with large numbers of devices. It also means that filesystems with different-sized devices will end up with differing-width stripes as the filesystem fills up, and some space may be wasted when the smaller devices are full.

Both of these issues could be addressed by specifying a fixed-width stripe, always running over exactly the same number of devices. This capability is not yet implemented, though.

Personal tools