On Sep 27, 2013, at 9:07 AM, Johannes Hirte <johannes.hirte@xxxxxxxxxxxxx> wrote: > On Tue, 24 Sep 2013 22:34:20 -0600 > Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > >> OK so I think I'm narrowing this down to just the systemd journal, >> and it's not checksums that are corrupted, it's the journal itself. > > I doubt it's systemd-dependent, I did not intend to indicate only systemd journal can trigger this, but rather on my system those appear to be the only affected files. Anything that has the same write behavior as systemd-journald probably has the same problem. > > on a fsck and scrub tells me that there are unfixable csum errors. The scrub should cause messages to appear in dmesg that include a pathname to the affected files, which might hint at what has the same write behavior. Even though a fix has been sent to stable for the systemd journal triggered issue, you should still find out what's being corrupted in your situation in case the write behaviors are different yet are still triggering corruption. 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
