Submission type

• Bug report
• Request for enhancement (RFE)

NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!

systemd version the issue has been seen with

229

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

Ubuntu 16.04

In case of bug report: Expected behaviour you didn't see

A single line of output:

$ journalctl --vacuum-size=2G
Vacuuming done, freed 0B of archived journals on disk.

In case of bug report: Unexpected behaviour you saw

Result is duplicated. It's unclear why:

$ journalctl --vacuum-size=2G
Vacuuming done, freed 0B of archived journals on disk.
Vacuuming done, freed 0B of archived journals on disk.

In case of bug report: Steps to reproduce the problem

1. Start with Storage=auto, but /var/log/journal not created
2. Accumulate logs
3. Update journald.conf to set Storage=persistent
4. systemctl restart systemd-journald

5. At this point you should have logs in both /run/log/journal and /var/log/journal

6. journalctl --vacuum-size=2G

I suspect what's happen is that both /var/log/journal and /run/log/journal are getting vacuumed. It would help to clarify both which directories are vacuumed and that one is in memory, not on disk:

Vacuuming done on disk at /var/log/journal. Freed 0B of archived journals.
Vacuuming done in memory at /run/log/journal. Freed 0B of archived journals.