On Oct 16, 2014, at 5:17 AM, Tomasz Torcz <tomek@xxxxxxxxxxxxxx> wrote: > > Broken files are in /var/log/journal directory. This directory > is set NOCOW with chattr, all the files within too. > > Example of broken file: > system@0005057fe87730cf-6d3d85ed59bd70ae.journal~ What do you get for 'journalctl --verify' ? I'm curious if any journal files are considered corrupt by journalctl, and if there's parity between journalctl and dd_rescue when it comes to good/bad journals. > > When read with dd_rescue, there are many I/O errors > reported, the summary looks like that (x = error): >> -..-..xxxxxxxxx---x.-..-..-...-..-..-...-< 100% > > Reads with cat, hexdump fails with: > read(4, 0x1001000, 65536) = -1 EIO (Input/output error) Yeah weird, I'd expect in any case that there'd be a kernel message, whether it's a Btrfs or hardware problem. Chris Murphy -- 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
