From: "Goffredo Baroncelli <kreijack@libero.it>" <kreijack@libero.it>
To: <lists@colorremedies.com>
Cc: systemd Mailing List <systemd-devel@lists.freedesktop.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: R: Re: Slow startup of systemd-journal on BTRFS
Date: Thu, 12 Jun 2014 13:05:01 +0200 (CEST) [thread overview]
Message-ID: <1008028489.2721751402571101092.JavaMail.defaultUser@defaultHost> (raw)
>----Messaggio originale----
>Da: lists@colorremedies.com
>Data: 12/06/2014 2.40
>A: <kreijack@inwind.it>, "Goffredo Baroncelli"<kreijack@libero.it>
>Cc: "systemd Mailing List"<systemd-devel@lists.freedesktop.org>, "linux-btrfs"
<linux-btrfs@vger.kernel.org>
>Ogg: Re: Slow startup of systemd-journal on BTRFS
>
>
>On Jun 11, 2014, at 3:28 PM, Goffredo Baroncelli <kreijack@libero.it> wrote:
>>
>> If someone is able to suggest me how FRAGMENT the log file, I can try to
collect more scientific data.
>
>So long as you're not using compression, filefrag will show you fragments of
systemd-journald journals. I can vouch for the behavior
> you experience without xattr +C or autodefrag, but further it also causes
much slowness when reading journal contents. LIke if I want to
> search all boots for a particular error message to see how far back it
started, this takes quite a bit longer than on other file systems.
> So far I'm not experiencing this problem with autodefrag or any other
negative side effects, but my understanding is this code is still in flux.
>
>Since the journals have their own checksumming I'm not overly concerned about
setting xattr +C.
This is true; but it can be a general solution: the checksum of the data are
needed during a
scrub and/or a RAID rebuilding.
I want to investigate doing an explicit defrag once a week.
>
>Chris Murphy
G.Baroncelli
next reply other threads:[~2014-06-12 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 11:05 Goffredo Baroncelli <kreijack@libero.it> [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-12 11:07 R: Re: Slow startup of systemd-journal on BTRFS Goffredo Baroncelli <kreijack@libero.it>
2014-06-12 11:13 Goffredo Baroncelli <kreijack@libero.it>
2014-06-12 12:37 ` Duncan
2014-06-12 23:24 ` Dave Chinner
2014-06-13 22:19 ` Goffredo Baroncelli
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=1008028489.2721751402571101092.JavaMail.defaultUser@defaultHost \
--to=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=systemd-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.