From: Josef Bacik <jbacik@fusionio.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: balance induced csum errors, systemd-journal
Date: Wed, 25 Sep 2013 08:30:51 -0400 [thread overview]
Message-ID: <20130925123051.GD18681@localhost.localdomain> (raw)
In-Reply-To: <013CDB89-72B2-4276-BCE9-0177CA90D840@colorremedies.com>
On Tue, Sep 24, 2013 at 11:44:15PM -0600, Chris Murphy wrote:
>
> On Sep 24, 2013, at 10:34 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
> > And how would I go about setting /var/log/journal contents to inherit nodatacow? Possible?
>
> chattr +C /var/log/journal
>
> Resolved the problem. Whether this is an appropriate long term fix that systemd should apply to this directory, I don't know.
>
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. Looking
at the systemd code it isn't doing O_DIRECT, which is how you usually end up
with this sort of situation. So it is likely a bug on our side, I will try and
track it down today. Thanks for narrowing this down,
Josef
next prev parent reply other threads:[~2013-09-25 12:30 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 [this message]
2013-09-25 14:56 ` Chris Murphy
2013-09-25 15:08 ` Josef Bacik
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=20130925123051.GD18681@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).