Description of problem: Journal can grow as big as the partition it is on. This is usually the root, which cause troubles. There should be a default maximum size or maximum numbers of days or maybe both. Version-Release number of selected component (if applicable): mga5 How reproducible: always Steps to Reproduce: 1. 2. 3.
(In reply to Tamás Hajdu from comment #0) > Description of problem: > Journal can grow as big as the partition it is on. This is usually the root, > which cause troubles. > There should be a default maximum size or maximum numbers of days or maybe > both. > @ Colin Not sure whether this is related, forget what I write if it isn't and doesn't help: Recently in a cauldron ( with systemd 229) I saw messages that the journal was set to a maximum size of 2GB, but it kept growing bigger than that, anyway, and instead of deleting the oldest part, it started only partially storing what was new. Sorry for having forgotten to report that. I've deleted 80% of the logs before installing systemd 230.
CC: (none) => marja11Assignee: bugsquad => mageia
hm, IIRC we fixed it once to have a limit of "leave atleast 15% free diskspace always"... but maybe that has been changed/broken since that...
CC: (none) => tmb
closing
Status: NEW => RESOLVEDResolution: (none) => INVALID