From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: price to pay for nocow file bit?
Date: Sat, 10 Jan 2015 13:23:14 +0100 [thread overview]
Message-ID: <2224067.qJDVSVqWin@merkaba> (raw)
In-Reply-To: <10396011.VnMcUEBNIZ@merkaba>
Am Samstag, 10. Januar 2015, 13:00:23 schrieben Sie:
> I have seen this setting before, but I thought, well, logs would be good to
> keep. But for the SSD based laptop I will try volatile storage now. I will
> see whether I missed a longer history, but I reduced it before anyway to a
> 14 day maximum retention time already, cause systemd used 1,1 GiB of my
> root partition for logs while rsyslog + logrotate used much less[1]. And I
> have yet not seen the immediate benefit for me here on this laptop to
> justify using up that much resources just for logging. So for me its a
> useless waste of resources currently. (This may be different on a server or
> anywhere where logfiles matter more, but then, when I consider some of our
> server VMs with just 4 to 5 GiB VMDK file, journald on Debian in default
> settings could easily fill the remaining space on some of them. Which I
> would consider a regression.)
Okay, scratch that.
journald is adaptive to the remaining space on the disk AFAIK.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-01-10 12:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 17:43 price to pay for nocow file bit? Lennart Poettering
2015-01-07 20:10 ` Josef Bacik
2015-01-07 21:05 ` Goffredo Baroncelli
2015-01-07 22:06 ` Josef Bacik
2015-01-08 6:30 ` Duncan
2015-01-10 12:00 ` Martin Steigerwald
2015-01-10 12:23 ` Martin Steigerwald [this message]
2015-01-08 8:24 ` Chris Murphy
2015-01-08 8:35 ` Koen Kooi
2015-01-08 13:30 ` Lennart Poettering
2015-01-08 18:24 ` Konstantinos Skarlatos
2015-01-08 18:48 ` Goffredo Baroncelli
2015-01-09 15:52 ` David Sterba
2015-01-10 10:30 ` Martin Steigerwald
2015-01-11 20:39 ` Chris Murphy
2015-01-08 15:56 ` Zygo Blaxell
2015-01-08 16:53 ` Lennart Poettering
2015-01-08 18:36 ` Zygo Blaxell
2015-01-09 15:41 ` David Sterba
2015-01-09 16:14 ` Zygo Blaxell
2015-01-08 20:42 ` Roger Binns
2015-01-15 19:06 ` Chris Mason
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=2224067.qJDVSVqWin@merkaba \
--to=martin@lichtvoll.de \
--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).