Re: price to pay for nocow file bit?

[Martin Steigerwald <Martin@lichtvoll.de>]

Am Donnerstag, 8. Januar 2015, 06:30:59 schrieb Duncan:
> FWIW, I'm systemd on btrfs here, but I use syslog-ng for my non-volatile 
> logs and have Storage=volatile in journald.conf, using journald only for 
> current-session, where unit status including last-10-messages makes 
> troubleshooting /so/ much easier. =:^)  Once past current-session, text 
> logs are more useful to me, which is where syslog-ng comes in.  Each to 
> its strength, and keeping the journals from wearing the SSDs[1] is a very 
> nice bonus. =:^)

Nice, I try this as well.

Cause while journalctl provides some nice stuff to query the logs, even by field 
or time and what not, frankly on my laptop, I don´t care.

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.)

[1] systemd: journal is quite big compared to rsyslog output
https://bugs.debian.org/773538

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7