At Sat, 10 Nov 2007 20:46:40 +0100, Arno Wagner <wagner@xxxxxxxxxxxxxx> wrote: > Another thing I found wise to check in case of corruption is main > memory. 24 hours of memtest86+ usually do the trick. I have seen corruptions (3rd party Infineon memory running at 400MHz, specified for 400MHz) that are not catched by memtest86+ reliably. Running Linux kernel compilation repeatedly is more stressful than memtest86+. > Apart from that, I don't feel that my time has been wasted. > To know about a possible source of corruption is always > interesting. And dm-crypt just got a bit more trustworthy, > because it was scrutinized carefully. Maybe adding a little tool to cryptsetup to check for corruptions makes sense. --- Fruhwirth Clemens - http://clemens.endorphin.org --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
