On Sun, Sep 05, 2010 at 06:42:28PM +0200, Milan Broz wrote: > On 09/05/2010 02:34 PM, BOBA FETT wrote: > > Alright guys, I think I identified my issue. Just wanted to let you > > know .... > > > > A bad memory module :-( > > welcome to the club - this is at least 5th report which was caused > by broken RAM :-) > > > I think we should add this to FAQ. > raid5 + dm-crypt (+ XFS) seems to be nice hw stress test... > > Milan I will add an item. Fortunately I have not been hit myself by RAM problems it 7 years, but before I had one module with a weak bit in a 22 machine cluster with process migration. That was fun! Arno > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt > -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
