-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-11 18:44, Chris Murphy wrote:
journald can be configured to use however much persistent storage you want; it can also be configured to use only volatile storage.
Even when you tell it to use volatile storage, it uses a lot of disk space: minas-tirith:~ # journalctl --disk-usage Journals take up 74.3M on disk. minas-tirith:~ # uptime 19:34pm up 4 days 21:29, 25 users, load average: 0.11, 0.21, 0.20 minas-tirith:~ # ls /var/log/jo* ls: cannot access /var/log/jo*: No such file or directory minas-tirith:~ # A problem with journald is that you can not purge it of messages by classes, like erase all nntp entries. They take most of the megabytes above.
Btrfs uses substantially less metadata at mkfs time compared to XFS,
Really? I have to test that, because I know XFS takes very little. However, the big problem is snapshooting. On small rotating disks I would rather prefer reiserfs. And on flash stickes, I would prefer f2fs, when it becomes available. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWhVboACgkQja8UbcUWM1yybAD8DMM0b5sSpJoGir6TNMhkHzMq cpJXhmJ/nMSmfh4SIUAA/j8fPDDRuMvBgEGsqkyZueVElJgSBo8yoovFvYeE+tF9 =1wZn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org