On Thu, Apr 13, 2017 at 10:45:09AM +0200, Marc Haber wrote: > On Tue, Apr 11, 2017 at 06:15:02PM +0200, Adam Borowski wrote: > > Ouch, this is generally harmless unless your disk lies about barriers. > > Btrfs absolutely depends on them, and tends to suffer catastrophic > > corruption if writes were reordered when they shouldn't. > > So if the disk would actually lie, I would have had much trouble even > earlier. It's an SSD from 2013 or 2014, I think from Kingston. The box > is offline and remote at the moment, so I cannot give the exact type.
I have re-built the btrfs and restored from backup, so I can access the disk again. It's a Crucial/Micron RealSSD m4/C400/P400 M4-CT256M4SSD1 with 256 GB Capacity. I do have an image of the bad btrfs that makes the kernel oops on mount, reproducibly. Does this help in debugging? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
