btrfs and jfs have silent data corruption protection, but it could be nice to have this at block layer, since some databases (innodb at mysql) can use block device to allocate information (as a performace boost), and since i know, it don´t have silent data corruption protection... a solution at block device is better than filesystem? yes and no, but at block device we can use with any filesystem, even with fat16 or other old filesystem we could add more features in future (like jornaling) but i think just data integrity layer is nice... there´s others features like reallocation (when write to a silent write detected block, realloc it to another block like good SSD do) 2012/8/2 Roman Mamedov <rm@xxxxxxxxxx>: > On Thu, 02 Aug 2012 10:13:55 -0700 > Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx> wrote: > >> The only ways I know of to currently detect/repair silent data >> corruption are via the use of T10-DIF on SAS drives with 520-byte >> sectors and embedded per block CRCs (bytes 513-520) or via a patented >> algorithm used in a commercial Linux software RAID product >> (www.streamscale.com). > > Well, you can simply use BTRFS RAID1/RAID10 (RAID5/6 to come some time soon). > It has per block checksums and auto-healing from other drive(s) if data on > some drive turns out not to match the checksums anymore. > > -- > With respect, > Roman > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > "Stallman had a printer, > with code he could not see. > So he began to tinker, > and set the software free." -- Roberto Spadim Spadim Technology / SPAEmpresarial -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html