Seriously people, some of the BEST linux documentation available comes from the Arch and Gentoo wikis. WE ARE YOUR TEST BED. I don't care if you are using Debian, Fedora, Ubuntu or whatever... if you have a question, check the Arch and Gentoo wikis. ONE OF THEM probably has an answer because a lot of other distros documentation is outdated or incomplete.
Now, Ramiliez, to answer your question.
From the arch wiki: https://wiki.archlinux.org/index.php/Systemd#Journal
Journal size limit
If the journal is persistent (non-volatile), its size limit is set to a default value of 10% of the size of the respective file system. For example, with /var/log/journal located on a 50 GiB root partition this would lead to 5 GiB of journal data. The maximum size of the persistent journal can be controlled by SystemMaxUse in /etc/systemd/journald.conf, so to limit it for example to 50 MiB uncomment and edit the corresponding line to:
Refer to man journald.conf for more info.Code:SystemMaxUse=50M
So how can i backup journald logs?
How come that journal is 5.9M while it contains just 44 entries
[root@localhost journal]# du -h
And btw reducing log size also removed a lot of logs but instead of keeping the newest logs im left garbage from 6 days
In my experience, if your log files are in a binary format then you are doing it wrong (TM).
Especially on Linux, you have just thrown all the traditional text processing tools (sed, grep etc) out the window.
There are ways to index text files for faster access etc. It's also easy to limit the size of the log file, or just create a new file whenever the size reaches a certain limit.
Now I will need a special tool just to read the log file? Microsoft went down that alley, and failed. Log files on Windows are horrible and inaccessible. Don't do that to Linux.
The only question here is what Fedora does by default, and honestly, who cares? Nothing is stopping you from using a different system logger, all messages are forwarded to a socket at /run/systemd/journal/syslog. You can tell journalctl not to store logs and have your syslog daemon listen on that socket, or you can run both. If you're unable to make these changes, chances are that you're unable to actually make use of the text logs, too.
0 is the default (which turns it off) Journal entries older than the specified time limit (in seconds) will be automatically deleted. You may append "year" "month" "week" "day" "h" or "m" to over ride the default time unit of seconds.