From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: "btr >> linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: lennart Poettering <lennart@poettering.net>
Subject: Systemd 219 journald now sets the FS_NOCOW file flag for its journal files, possibly breaking RAID repairs.
Date: Thu, 19 Feb 2015 16:30:37 +0200 [thread overview]
Message-ID: <54E5F38D.4070104@gmail.com> (raw)
Systemd 219 now sets the special FS_NOCOW file flag for its journal
files[1]. This unfortunately breaks the ability to repair the journal on
RAID 1/5/6 btrfs volumes, should a bad sector happen to appear there. Is
this something that can be configured for systemd? Is btrfs going to
someday fix the fragmentation problem, making this option reduntant?
[1]
http://lists.freedesktop.org/archives/systemd-devel/2015-February/028447.html
* journald now sets the special FS_NOCOW file flag for its
journal files. This should improve performance on btrfs, by
avoiding heavy fragmentation when journald's write-pattern
is used on COW file systems. It degrades btrfs' data
integrity guarantees for the files to the same levels as for
ext3/ext4 however. This should be OK though as journald does
its own data integrity checks and all its objects are
checksummed on disk. Also, journald should handle btrfs disk
full events a lot more gracefully now, by processing SIGBUS
errors, and not relying on fallocate() anymore.
next reply other threads:[~2015-02-19 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 14:30 Konstantinos Skarlatos [this message]
2015-02-19 17:51 ` Systemd 219 journald now sets the FS_NOCOW file flag for its journal files, possibly breaking RAID repairs Chris Murphy
2015-02-19 21:23 ` Duncan
2015-02-19 22:57 ` Duncan
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=54E5F38D.4070104@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=lennart@poettering.net \
--cc=linux-btrfs@vger.kernel.org \
/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).