[opensuse][42.1] journal size & space consumption
Is this normal? # ls -hgGrt syst* -rw-r----- 1 104M Feb 25 2016 system@143191c9b76b43be9e6acc485edf3130-000000000001db3e-00052a40090a1bc3.journal -rw-r----- 1 104M Mar 27 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000038583-00052ca4556047dd.journal -rw-r----- 1 112M Apr 26 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000052816-00052f08d74c92e1.journal -rw-r----- 1 112M May 27 2016 system@143191c9b76b43be9e6acc485edf3130-000000000006ffaf-0005316d4583cdc6.journal -rw-r----- 1 120M Jun 26 2016 system@143191c9b76b43be9e6acc485edf3130-000000000008c564-000533d1a57e2ca9.journal -rw-r----- 1 120M Jul 27 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000a9cf9-00053635f1d92c62.journal -rw-r----- 1 120M Aug 26 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000c7396-0005389a73bd3d87.journal -rw-r----- 1 32M Sep 2 2016 system@00053b8b6c6c6cbd-56c57c7b8162d802.journal~ -rw-r----- 1 104M Sep 26 2016 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000000001-00053b8b6b67376c.journal -rw-r----- 1 120M Oct 27 00:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000010491a-00053d6d298c2600.journal -rw-r----- 1 112M Nov 26 10:20 system@0773dbc1bed548d3aaa4fd315577dca4-00000000001220cd-00053fd184f699a0.journal -rw-r----- 1 16M Nov 28 04:06 system@0773dbc1bed548d3aaa4fd315577dca4-000000000013e630-00054235e9890817.journal -rw-r----- 1 72M Dec 28 14:35 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000140006-00054258cb34686c.journal -rw-r----- 1 120M Jan 28 01:20 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000152f9f-000544bd34623870.journal -rw-r----- 1 112M Feb 27 12:05 system@0773dbc1bed548d3aaa4fd315577dca4-000000000017156e-00054721b64c1142.journal -rw-r----- 1 112M Mar 29 23:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000018e526-000549863842cec3.journal -rw-r----- 1 48M Apr 9 18:38 system.journal That's 1,679,360K in 17 files. That 48M last one contains >113k lines. '# journalctl | grep "systemd\[" | wc -l' produced 1,508,572. http://fm.no-ip.com/Tmp/SUSE/421/mbdjrnl.txt 116k, 1210 lines is the output from journalctl | grep mbd | grep -v <########> that took about 4 minutes of 100% CPU to generate. Surely those mbd lines can't be normal, though I see they stopped several weeks ago, likely the time of last reboot, which followed fresh updates. How much of this is normal or expected? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [04-09-17 19:26]:
Is this normal? # ls -hgGrt syst* -rw-r----- 1 104M Feb 25 2016 system@143191c9b76b43be9e6acc485edf3130-000000000001db3e-00052a40090a1bc3.journal -rw-r----- 1 104M Mar 27 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000038583-00052ca4556047dd.journal -rw-r----- 1 112M Apr 26 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000052816-00052f08d74c92e1.journal -rw-r----- 1 112M May 27 2016 system@143191c9b76b43be9e6acc485edf3130-000000000006ffaf-0005316d4583cdc6.journal -rw-r----- 1 120M Jun 26 2016 system@143191c9b76b43be9e6acc485edf3130-000000000008c564-000533d1a57e2ca9.journal -rw-r----- 1 120M Jul 27 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000a9cf9-00053635f1d92c62.journal -rw-r----- 1 120M Aug 26 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000c7396-0005389a73bd3d87.journal -rw-r----- 1 32M Sep 2 2016 system@00053b8b6c6c6cbd-56c57c7b8162d802.journal~ -rw-r----- 1 104M Sep 26 2016 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000000001-00053b8b6b67376c.journal -rw-r----- 1 120M Oct 27 00:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000010491a-00053d6d298c2600.journal -rw-r----- 1 112M Nov 26 10:20 system@0773dbc1bed548d3aaa4fd315577dca4-00000000001220cd-00053fd184f699a0.journal -rw-r----- 1 16M Nov 28 04:06 system@0773dbc1bed548d3aaa4fd315577dca4-000000000013e630-00054235e9890817.journal -rw-r----- 1 72M Dec 28 14:35 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000140006-00054258cb34686c.journal -rw-r----- 1 120M Jan 28 01:20 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000152f9f-000544bd34623870.journal -rw-r----- 1 112M Feb 27 12:05 system@0773dbc1bed548d3aaa4fd315577dca4-000000000017156e-00054721b64c1142.journal -rw-r----- 1 112M Mar 29 23:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000018e526-000549863842cec3.journal -rw-r----- 1 48M Apr 9 18:38 system.journal
That's 1,679,360K in 17 files.
That 48M last one contains >113k lines.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
what does "journalctl --disk-usage" provide. # journalctl --disk-usage Archived and active journals take up 2.0M in the file system. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan composed on 2017-04-09 20:14 (UTC-0400):
* Felix Miata composed:
Is this normal? ... -rw-r----- 1 48M Apr 9 18:38 system.journal
That's 1,679,360K in 17 files.
That 48M last one contains >113k lines.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
what does "journalctl --disk-usage" provide.
# journalctl --disk-usage Archived and active journals take up 2.0M in the file system.
Even just the newest file here is >20X yours. :-( # journalctl --disk-usage Journals take up 1.7G on disk. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [04-09-17 20:29]:
Patrick Shanahan composed on 2017-04-09 20:14 (UTC-0400):
* Felix Miata composed:
Is this normal? .. -rw-r----- 1 48M Apr 9 18:38 system.journal
That's 1,679,360K in 17 files.
That 48M last one contains >113k lines.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
what does "journalctl --disk-usage" provide.
# journalctl --disk-usage Archived and active journals take up 2.0M in the file system.
Even just the newest file here is >20X yours. :-(
# journalctl --disk-usage Journals take up 1.7G on disk.
have you set a limit for journal files? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan composed on 2017-04-09 21:31 (UTC-0400):
what does "journalctl --disk-usage" provide.
# journalctl --disk-usage Archived and active journals take up 2.0M in the file system.
Even just the newest file here is >20X yours. :-(
# journalctl --disk-usage Journals take up 1.7G on disk.
have you set a limit for journal files?
No. The journal author or packager should have provided something resembling a sane default, or a pointer thereto, as no examples have been provided in journald.conf. Its man page describes defaults that are percents of filesystem sizes, not very helpful. Test installations that are up only an hour or three here and there provide no clues to any need for a machine up for weeks or months at a time for anything other than a default config. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [04-09-17 21:59]:
Patrick Shanahan composed on 2017-04-09 21:31 (UTC-0400):
what does "journalctl --disk-usage" provide.
# journalctl --disk-usage Archived and active journals take up 2.0M in the file system.
Even just the newest file here is >20X yours. :-(
# journalctl --disk-usage Journals take up 1.7G on disk.
have you set a limit for journal files?
No. The journal author or packager should have provided something resembling a sane default, or a pointer thereto, as no examples have been provided in journald.conf. Its man page describes defaults that are percents of filesystem sizes, not very helpful. Test installations that are up only an hour or three here and there provide no clues to any need for a machine up for weeks or months at a time for anything other than a default config.
journalctl --help --vacuum-size=BYTES Reduce disk usage below specified size google journalctl config size SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, SystemMaxFiles=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize=, RuntimeMaxFiles= Enforce size limits on the journal files stored. The options prefixed with "System" apply to the journal files when stored on a persistent file system, more specifically /var/log/journal. The options prefixed with "Runtime" apply to the journal files when stored on a volatile in-memory file system, more specifically /run/log/journal. The former is used only when /var is mounted, writable, and the directory /var/log/journal exists. Otherwise, only the latter applies. Note that this means that during early boot and if the administrator disabled persistent logging, only the latter options apply, while the former apply if persistent logging is enabled and the system is fully booted up. journalctl and systemd-journald ignore all files with names not ending with ".journal" or ".journal~", so only such files, located in the appropriate directories, are taken into account when calculating current disk usage. SystemMaxUse= and RuntimeMaxUse= control how much disk space the journal may use up at most. SystemKeepFree= and RuntimeKeepFree= control how much disk space systemd-journald shall leave free for other uses. systemd-journald will respect both limits and use the smaller of the two values. The first pair defaults to 10% and the second to 15% of the size of the respective file system, but each value is capped to 4G. If the file system is nearly full and either SystemKeepFree= or RuntimeKeepFree= are violated when systemd-journald is started, the limit will be raised to the percentage that is actually free. This means that if there was enough free space before and journal files were created, and subsequently something else causes the file system to fill up, journald will stop using more space, but it will not be removing existing files to reduce the footprint again, either. SystemMaxFileSize= and RuntimeMaxFileSize= control how large individual journal files may grow at most. This influences the granularity in which disk space is made available through rotation, i.e. deletion of historic data. Defaults to one eighth of the values configured with SystemMaxUse= and RuntimeMaxUse=, so that usually seven rotated journal files are kept as history. Specify values in bytes or use K, M, G, T, P, E as units for the specified sizes (equal to 1024, 1024², … bytes). Note that size limits are enforced synchronously when journal files are extended, and no explicit rotation step triggered by time is needed. SystemMaxFiles= and RuntimeMaxFiles= control how many individual journal files to keep at most. Note that only archived files are deleted to reduce the number of files until this limit is reached; active files will stay around. This means that, in effect, there might still be more journal files around in total than this limit after a vacuuming operation is complete. This setting defaults to 100. also: /etc/systemd/journald.conf /etc/systemd/journald.conf.d/*.conf /run/systemd/journald.conf.d/*.conf /usr/lib/systemd/journald.conf.d/*.conf and: https://wiki.manjaro.org/index.php?title=Limit_the_size_of_.log_files_%26_th... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan composed on 2017-04-09 22:43 (UTC-0400):
journalctl --help --vacuum-size=BYTES Reduce disk usage below specified size
google journalctl config size SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, SystemMaxFiles=,...
Same example-free blather that's in the man page. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan composed on 2017-04-09 22:43 (UTC-0400):
https://wiki.manjaro.org/index.php?title=Limit_the_size_of_.log_files_%26_th...
"There is usually no need to interfere with the maximum size of the journal," O_O At least it has examples, so thanks for the link. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2017 09:55 PM, Felix Miata wrote:
Patrick Shanahan composed on 2017-04-09 22:43 (UTC-0400):
https://wiki.manjaro.org/index.php?title=Limit_the_size_of_.log_files_%26_th...
"There is usually no need to interfere with the maximum size of the journal,"
O_O
At least it has examples, so thanks for the link.
I always set: SystemMaxUse=50M in /etc/systemd/journald.conf and never have any problems: # journalctl --disk-usage Archived and active journals take up 56.2M on disk. (OK, so active takes up 6.2M while running -- I can live with that :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-10 10:58, David C. Rankin wrote:
On 04/09/2017 09:55 PM, Felix Miata wrote:
Patrick Shanahan composed on 2017-04-09 22:43 (UTC-0400):
https://wiki.manjaro.org/index.php?title=Limit_the_size_of_.log_files_%26_th...
"There is usually no need to interfere with the maximum size of the journal,"
O_O
At least it has examples, so thanks for the link.
I always set:
SystemMaxUse=50M
in
The issue is then that you can not analyze old problems. The default for syslog is one year of logs. I want a reliable and good replacement for syslog, not a half cooked thing. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 04/10/2017 04:09 AM, Carlos E. R. wrote:
The issue is then that you can not analyze old problems. The default for syslog is one year of logs.
I want a reliable and good replacement for syslog, not a half cooked thing.
We need to look at definitions. It does not get rid of any logs, I still have all logs going back to my 2015 install on another arch with SystemMaxUse=320M, e.g. 02:01 phoinix:~> sudo journalctl --disk-usage Archived and active journals take up 360.0M in the file system. Here all my logs from initial install (second boot after network install) are there: 02:07 phoinix:~> jcnl -b2 -n100 -- Logs begin at Sat 2015-08-08 17:17:21 CDT, end at Wed 2017-04-12 02:07:52 CDT. -- Aug 29 13:20:29 phoinix systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected Aug 29 13:20:29 phoinix systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected Aug 29 13:20:29 phoinix systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected Aug 29 13:20:29 phoinix systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected <snip> I will have to research just what the limit is for SystemMaxUse -- David C. Rankin, J.D.,P.E.
On 2017-04-12 09:13, David C. Rankin wrote:
On 04/10/2017 04:09 AM, Carlos E. R. wrote:
The issue is then that you can not analyze old problems. The default for syslog is one year of logs.
I want a reliable and good replacement for syslog, not a half cooked thing.
We need to look at definitions. It does not get rid of any logs, I still have all logs going back to my 2015 install on another arch with SystemMaxUse=320M, e.g.
02:01 phoinix:~> sudo journalctl --disk-usage Archived and active journals take up 360.0M in the file system.
This system I posted data, is at 1 GB after 4 months. At this rate, it can reach 4 GB per year. The syslog data, which I also keep, is orders of size smaller and searches way much faster. On my main computer, the journal grows to a gigabyte in weeks. No way it can keep years of data. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-04-12 09:13, David C. Rankin wrote:
On 04/10/2017 04:09 AM, Carlos E. R. wrote:
The issue is then that you can not analyze old problems. The default for syslog is one year of logs.
I want a reliable and good replacement for syslog, not a half cooked thing.
We need to look at definitions. It does not get rid of any logs, I still have all logs going back to my 2015 install on another arch with SystemMaxUse=320M, e.g.
02:01 phoinix:~> sudo journalctl --disk-usage Archived and active journals take up 360.0M in the file system.
This system I posted data, is at 1 GB after 4 months. At this rate, it can reach 4 GB per year. The syslog data, which I also keep, is orders of size smaller and searches way much faster.
On a smallish mailserver where I archive mail, messages and firewall logs, it generated 1.7G (compressed) over three years.
On my main computer, the journal grows to a gigabyte in weeks. No way it can keep years of data.
Yeah, use a syslog daemon for that. -- Per Jessen, Zürich (14.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-10 03:58, Felix Miata wrote:
Patrick Shanahan composed on 2017-04-09 21:31 (UTC-0400):
# journalctl --disk-usage Journals take up 1.7G on disk.
have you set a limit for journal files?
No. The journal author or packager should have provided something resembling a sane default, or a pointer thereto, as no examples have been provided in journald.conf. Its man page describes defaults that are percents of filesystem sizes, not very helpful. Test installations that are up only an hour or three here and there provide no clues to any need for a machine up for weeks or months at a time for anything other than a default config.
Same here. I assume that the default will keep logs same as syslog does, which is a year of logs. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 04/10/2017 01:23 AM, Felix Miata wrote:
That's 1,679,360K in 17 files.
That 48M last one contains >113k lines.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
http://fm.no-ip.com/Tmp/SUSE/421/mbdjrnl.txt 116k, 1210 lines is the output from journalctl | grep mbd | grep -v <########> that took about 4 minutes of 100% CPU to generate. Surely those mbd lines can't be normal, though I see they stopped several weeks ago, likely the time of last reboot, which followed fresh updates.
How much of this is normal or expected?
It is normal and wanted behavior that journald is big and slow. The slowness and unusability is it's major feature. To simulate the old-fashioned behavior I always install syslog, remove persistent journald storage and limit the journal size. $ rm -rf /var/log/journal # /etc/systemd/journald.conf SystemMaxUse=16M RuntimeMaxUse=8M cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-10 09:23, Rüdiger Meier wrote:
On 04/10/2017 01:23 AM, Felix Miata wrote:
How much of this is normal or expected?
It is normal and wanted behavior that journald is big and slow. The slowness and unusability is it's major feature.
:-)
To simulate the old-fashioned behavior I always install syslog, remove persistent journald storage and limit the journal size.
$ rm -rf /var/log/journal
# /etc/systemd/journald.conf SystemMaxUse=16M RuntimeMaxUse=8M
Or: Storage=none for nothing. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Felix Miata composed on 2017-04-09 19:23 (UTC-0400):
Is this normal? # ls -hgGrt syst* -rw-r----- 1 104M Feb 25 2016 system@143191c9b76b43be9e6acc485edf3130-000000000001db3e-00052a40090a1bc3.journal -rw-r----- 1 104M Mar 27 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000038583-00052ca4556047dd.journal -rw-r----- 1 112M Apr 26 2016 system@143191c9b76b43be9e6acc485edf3130-0000000000052816-00052f08d74c92e1.journal -rw-r----- 1 112M May 27 2016 system@143191c9b76b43be9e6acc485edf3130-000000000006ffaf-0005316d4583cdc6.journal -rw-r----- 1 120M Jun 26 2016 system@143191c9b76b43be9e6acc485edf3130-000000000008c564-000533d1a57e2ca9.journal -rw-r----- 1 120M Jul 27 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000a9cf9-00053635f1d92c62.journal -rw-r----- 1 120M Aug 26 2016 system@143191c9b76b43be9e6acc485edf3130-00000000000c7396-0005389a73bd3d87.journal -rw-r----- 1 32M Sep 2 2016 system@00053b8b6c6c6cbd-56c57c7b8162d802.journal~ -rw-r----- 1 104M Sep 26 2016 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000000001-00053b8b6b67376c.journal
In journald.conf I changed #SystemMaxUse= to SystemMaxUse=800M and restarted systemd-journald, after which were retained only those below
-rw-r----- 1 120M Oct 27 00:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000010491a-00053d6d298c2600.journal -rw-r----- 1 112M Nov 26 10:20 system@0773dbc1bed548d3aaa4fd315577dca4-00000000001220cd-00053fd184f699a0.journal -rw-r----- 1 16M Nov 28 04:06 system@0773dbc1bed548d3aaa4fd315577dca4-000000000013e630-00054235e9890817.journal -rw-r----- 1 72M Dec 28 14:35 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000140006-00054258cb34686c.journal -rw-r----- 1 120M Jan 28 01:20 system@0773dbc1bed548d3aaa4fd315577dca4-0000000000152f9f-000544bd34623870.journal -rw-r----- 1 112M Feb 27 12:05 system@0773dbc1bed548d3aaa4fd315577dca4-000000000017156e-00054721b64c1142.journal -rw-r----- 1 112M Mar 29 23:50 system@0773dbc1bed548d3aaa4fd315577dca4-000000000018e526-000549863842cec3.journal -rw-r----- 1 48M Apr 9 18:38 system.journal
That's 1,679,360K in 17 files.
which left 746,586K in 8 files.
That 48M last one contains >113k lines.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
http://fm.no-ip.com/Tmp/SUSE/421/mbdjrnl.txt 116k, 1210 lines is the output from journalctl | grep mbd | grep -v <########> that took about 4 minutes of 100% CPU to generate. Surely those mbd lines can't be normal, though I see they stopped several weeks ago, likely the time of last reboot, which followed fresh updates.
A subsequent 'journalctl | grep "systemd\[" | wc -l' took 95 seconds to complete, but still had CPU pegged the whole time. # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 11702 MB in 2.00 seconds = 5854.68 MB/sec Timing buffered disk reads: 504 MB in 3.01 seconds = 167.59 MB/sec
How much of this is normal or expected? Is this journal access lack of performance normal or expected??? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-10 09:36, Felix Miata wrote:
How much of this is normal or expected? Is this journal access lack of performance normal or expected???
Yes. It is slow even on static disks (see my data on another post). -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-04-10 01:23, Felix Miata wrote:
Is this normal? # ls -hgGrt syst*
...
That's 1,679,360K in 17 files.
That 48M last one contains >113k lines.
Isengard:~ # journalctl --disk-usage Archived and active journals take up 1.1G on disk.
'# journalctl | grep "systemd\[" | wc -l' produced 1,508,572.
819494 here.
http://fm.no-ip.com/Tmp/SUSE/421/mbdjrnl.txt 116k, 1210 lines is the output from journalctl | grep mbd | grep -v <########> that took about 4 minutes of 100% CPU to generate.
Isengard:~ # time journalctl | grep mbd | grep -v <########> -bash: syntax error near unexpected token `newline' -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (6)
-
Carlos E. R. -
David C. Rankin -
Felix Miata -
Patrick Shanahan -
Per Jessen -
Rüdiger Meier