From: Josef Bacik <jbacik@fusionio.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Josef Bacik <jbacik@fusionio.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: balance induced csum errors, systemd-journal
Date: Wed, 25 Sep 2013 11:08:55 -0400 [thread overview]
Message-ID: <20130925150855.GF18681@localhost.localdomain> (raw)
In-Reply-To: <A6A9156F-0502-4528-80D4-D61F48E4A7DE@colorremedies.com>
On Wed, Sep 25, 2013 at 08:56:52AM -0600, Chris Murphy wrote:
>
> On Sep 25, 2013, at 6:30 AM, Josef Bacik <jbacik@fusionio.com> wrote:
>
> >
> > That just disables cow which in turn disables csumming so it is a good solution
> > for you right now and gives me time ti figure out wtf is going on here.
>
> I think it's preventing the corruption of the journal logs, because I'm also no longer getting messages from systemd saying a log is corrupt. So I don't think the problem is solved just by not having csums. I'm thinking the csums were always correct, it was the data that was corrupting… or both data and csums were wrong.
>
> It seems that the way systemd-journal is writing to disk is handled differently only during balance operations. The corruption has never happened with days of normal usage (no balance). But happens within tens of seconds upon balance. Naturally something or other is always being written to the systemd-journal logs during a balance (someone logs in=journal entry, kernel reports extent found=journal entry, kernel reports moved chunk=journal entry).
>
I've reproduce it locally so I'll hopefully figure out what is going on soon.
Thanks,
Josef
next prev parent reply other threads:[~2013-09-25 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 21:57 balance induced csum errors Chris Murphy
2013-09-23 22:35 ` Chris Murphy
2013-09-24 21:36 ` Chris Murphy
2013-09-24 22:30 ` Chris Murphy
2013-09-25 4:34 ` balance induced csum errors, systemd-journal Chris Murphy
2013-09-25 5:44 ` Chris Murphy
2013-09-25 12:30 ` Josef Bacik
2013-09-25 14:56 ` Chris Murphy
2013-09-25 15:08 ` Josef Bacik [this message]
2013-09-25 6:38 ` Duncan
2013-09-27 15:07 ` Johannes Hirte
2013-09-27 16:22 ` Chris Murphy
2013-09-24 23:12 ` balance induced csum errors Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130925150855.GF18681@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).