Re: Journald retaining logs for only 10 days

[Nikolaus Rath <Nikolaus@xxxxxxxx>]

On Nov 14 2020, Uoti Urpala <uoti.urpala@xxxxxxxxxxx> wrote:
> On Sat, 2020-11-14 at 09:31 +0000, Nikolaus Rath wrote:
>> # journalctl --disk-usage
>> Archived and active journals take up 320.0M in the file system.
>> 
>> # journalctl > alllogs
>> # ls -lh alllogs 
>> -rw-r--r-- 1 root root 27M Nov 14 09:24 alllogs
>
> The journal stores a lot of metadata for each log entry, so the
> "alllogs" size is not a good indicator of disk space requirements.
> Use "journalctl -o verbose" to see all information that is actually
> stored.

# journalctl -o verbose -a > alllogs
# ls -lh alllogs 
-rw-r--r-- 1 root root 223M Nov 14 19:19 alllogs

Wow, that is a lot of overhead. However, this still isn't 320 MB, and
it doesn't take into account that journalctl is storing the data
compressed, and much of the output (the field names) most likely isn't
stored in this form.

I remain unconvinced...

Could someone else post an example of how many log entries they get per
MB of journal size on their system?

Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel