July 15, 20178 yr The RAID5/6 write hole is one of the remaing data integrity risks. Since 4.11 the Linux kernel has support for a journal device where writes to the array and parity are journaled for a number of stripes before they are written to the array devices. This can help in a case of crash to redo the last write operation and/or use the journaled data to reconstruct inconsistent information. Maybe this could be leveraged for unraid (or implemented in another way), in particular because unraid already is based heavily on a cache drive where this data could be written to. Even if this would require an additonal (smaller) ssd drive, it seems a like a good idea to add in unraid. Performance wise it should not really have in impact as these writes are on an SSD device and can be done in parallel to the array writes. The relevant changes in the linux kernel: Kernel 4.11.x: Journaled RAID4/5/6 to close the write hole Based in work started in Linux 4.4, this release adds journalling support to RAID4/5/6 in the MD layer (not to be confused with btrfs RAID). With a journal device configured (typically NVRAM or SSD), the "RAID5 write hole" is closed - a crash during degraded operations cannot result in data corruption. Recommended LWN article: A journal for MD/RAID5 Blog entry: Improving software RAID with a write-ahead log Code: commit Sorry for the Bold Face, but somehow the editior refuses to change it. Edited July 15, 20178 yr by Videodr0me
Archived
This topic is now archived and is closed to further replies.