On Sat, Jul 14, 2007 at 07:32:38PM -0700, Mr. James W. Laferriere wrote: > >So your disk throws a fit > > Actually it's brand new . Infant mortallity ? I at least have a > cold spare available . So Yes I am replacing that puppy . I'll drop it > into another system & give it the format command & see how much the user > bad block table grows . I'll bet I'll get a table full overflow on it . Manually keep both tables under supervision. I'd guess that if you send it a format, it will update the factory table (and move the user bad block table there). But most will retry writing to the bad sectors. And with a fully-fresh copy of the data, it will still be readable, and the blocks will be marked as ready-for-use, because that's better for performance.... > >And at some point at least 18 minutes after the raid incident you log > >CPU problems. > > I didn't notice the 18 Minute differance . Drats . I'm not sure how this happened, but the disk errror messages seem to have been logged by syslog, and the MCEs seem to have been copied from the console: They don't have the date attached....? Roger. -- ** R.E.Wolff@xxxxxxxxxxxx ** http://www.BitWizard.nl/ ** +31-15-2600998 ** ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ - 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
