Chris Murphy posted on Thu, 30 Jan 2014 23:13:36 -0700 as excerpted: > On Jan 30, 2014, at 11:10 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> > wrote: >> >> I'm also seeing many "Error reading 1647012864000, -1" with different >> block addresses (same -1 though), and also "1659900002304failed to load >> free space cache for block group" also with different numbers. Maybe >> hundreds of these. I'm not sure if this is due to the missing device, >> and it's reporting missing meta data? Or if the working device also has >> some problem, which depending on the configuration might implicate a >> single SATA controller. > > Sorry I'm being impatient since I'm away snowboarding tomorrow. The > above refers to parts of Johan's btrfs check output which hasn't yet > made it to the list. Break a leg! =:^) (If you've done much drama/acting you may know the reference; there's a traditional superstition that wishing someone .... luck is a hex and they'll forget their lines or worse! So you wish them to break a leg instead! =:^) I'm assuming the error reading errors are due to the missing device, with the round-robin trying to read the bad device 50% of the time, but if it was full raid1, then the existing copy should be found and read instead, assuming of course that the checksum verifies, so despite all the alarming looking noise, I believe it's harmless... assuming it was indeed full raid1 both data and metadata. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
