What do systemd “Vacuuming done, freed 0 bytes” messages mean?
I'm seeing messages like the following in my systemd journal:
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
What do these messages mean?
linux logs systemd
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
add a comment |
I'm seeing messages like the following in my systemd journal:
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
What do these messages mean?
linux logs systemd
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
1
It'sjournalddoing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newersystemdversions you should no longer see those messages.
– don_crissti
Aug 29 '15 at 9:18
add a comment |
I'm seeing messages like the following in my systemd journal:
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
What do these messages mean?
linux logs systemd
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
I'm seeing messages like the following in my systemd journal:
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 0 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
systemd-journald[52]: Vacuuming done, freed 4198400 bytes
What do these messages mean?
linux logs systemd
linux logs systemd
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
asked Aug 28 '15 at 18:34
user5071535user5071535
171214
171214
1
It'sjournalddoing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newersystemdversions you should no longer see those messages.
– don_crissti
Aug 29 '15 at 9:18
add a comment |
1
It'sjournalddoing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newersystemdversions you should no longer see those messages.
– don_crissti
Aug 29 '15 at 9:18
1
1
It's
journald doing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newer systemd versions you should no longer see those messages.– don_crissti
Aug 29 '15 at 9:18
It's
journald doing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newer systemd versions you should no longer see those messages.– don_crissti
Aug 29 '15 at 9:18
add a comment |
1 Answer
1
active
oldest
votes
Well, it's more of a journald log than a systemd log, here's what journalctl says about vacuum size:
journalctl(1) wrote:
--vacuum-size=,--vacuum-time=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running
--vacuum-size=has only an indirect effect on the output shown by--disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly,--vacuum-files=might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files.
edited 46 mins ago
Pablo Bianchi
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f226145%2fwhat-do-systemd-vacuuming-done-freed-0-bytes-messages-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well, it's more of a journald log than a systemd log, here's what journalctl says about vacuum size:
journalctl(1) wrote:
--vacuum-size=,--vacuum-time=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running
--vacuum-size=has only an indirect effect on the output shown by--disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly,--vacuum-files=might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files.
edited 46 mins ago
Pablo Bianchi
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
add a comment |
Well, it's more of a journald log than a systemd log, here's what journalctl says about vacuum size:
journalctl(1) wrote:
--vacuum-size=,--vacuum-time=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running
--vacuum-size=has only an indirect effect on the output shown by--disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly,--vacuum-files=might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files.
edited 46 mins ago
Pablo Bianchi
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
add a comment |
Well, it's more of a journald log than a systemd log, here's what journalctl says about vacuum size:
journalctl(1) wrote:
--vacuum-size=,--vacuum-time=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running
--vacuum-size=has only an indirect effect on the output shown by--disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly,--vacuum-files=might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files.
edited 46 mins ago
Pablo Bianchi
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
Well, it's more of a journald log than a systemd log, here's what journalctl says about vacuum size:
journalctl(1) wrote:
--vacuum-size=,--vacuum-time=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running
--vacuum-size=has only an indirect effect on the output shown by--disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly,--vacuum-files=might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files.
edited 46 mins ago
Pablo Bianchi
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
edited 46 mins ago
Pablo Bianchi
521612
edited 46 mins ago
Pablo Bianchi
521612
edited 46 mins ago
Pablo Bianchi
521612
521612
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
answered Aug 28 '15 at 18:39
Dan JanssenDan Janssen
261
261
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f226145%2fwhat-do-systemd-vacuuming-done-freed-0-bytes-messages-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It's
journalddoing implicit vacuuming (removing archived journal files). You're seeing those messages because of this commit. Lennart downgraded their priority to debug in this latter commit so with newersystemdversions you should no longer see those messages.– don_crissti
Aug 29 '15 at 9:18