Also, I know it was caused by bad RAM and that ram has since been removed. --- Eric Wolf (201) 316-6098 19w...@gmail.com
On Thu, Aug 31, 2017 at 2:33 PM, Hugo Mills <h...@carfax.org.uk> wrote: > On Thu, Aug 31, 2017 at 01:53:58PM -0400, Eric Wolf wrote: >> I'm having issues with a bad block(?) on my root ssd. >> >> dmesg is consistently outputting "BTRFS critical (device sda2): >> corrupt leaf, bad key order: block=293438636032, root=1, slot=11" >> >> "btrfs scrub stat /" outputs "scrub status for b2c9ff7b-[snip]-48a02cc4f508 >> scrub started at Wed Aug 30 11:51:49 2017 and finished after 00:02:55 >> total bytes scrubbed: 53.41GiB with 2 errors >> error details: verify=2 >> corrected errors: 0, uncorrectable errors: 2, unverified errors: 0" >> >> Running "btrfs check --repair /dev/sda2" from a live system stalls >> after telling me corrupt leaf etc etc then "11 12". CPU usage hits >> 100% and disk activity remains at 0. > > This error is usually attributable to bad hardware. Typically RAM, > but might also be marginal power regulation (blown capacitor > somewhere) or a slightly broken CPU. > > Can you show us the output of "btrfs-debug-tree -b 293438636032 /dev/sda2"? > > Hugo. > > -- > Hugo Mills | "You got very nice eyes, Deedee. Never noticed them > hugo@... carfax.org.uk | before. They real?" > http://carfax.org.uk/ | > PGP: E2AB1DE4 | Don Logan, Sexy Beast -- 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
