Corrupted log files

I am using Linux Mint 19.2 MATE.

My journalctl is keeping a massive 968 MBof logs as revealed by journalctl --disk-usage.

When I run journalctl --verify I discovered several corrupted log files:

Code:$ journalctl --disk-usage
Archived and active journals take up 968.0M in the file system.

$ journalctl --verify
3373f30: Invalid entry item (9/26 offset: 000000
3373f30: Invalid object contents: Bad message
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a5c1f4d21972-fe213732c19594e5.journal~:3373f30 (of 58720256 bytes, 91%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a5c1f4d21972-fe213732c19594e5.journal~ (Bad message)
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@e222d28928c9407e8e105b11f7a1a6f7-0000000000000001-00059fefd110477d.journal
396fa0: Data object references invalid entry at 133eae0
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a5c1f6f080a1-e540b91c1f07c23b.journal~:133d5a8 (of 25165824 bytes, 80%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a5c1f6f080a1-e540b91c1f07c23b.journal~ (Bad message)
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system.journal
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a5222f5655ef-26555e79b51ccd26.journal~
5600668: Data object references invalid entry at 5706748
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a75632c2350d-167a984be22382db.journal~:57064f8 (of 92274688 bytes, 98%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a75632c2350d-167a984be22382db.journal~ (Bad message)
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a75638b09fdc-244e55f426ed7a23.journal~
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@7f9b13c97fae46f78c4057282203cc4d-0000000000000001-0005a2b4e5e9ba07.journal
27fdfb0: Invalid entry item (1/21 offset: 000000
27fdfb0: Invalid object contents: Bad message
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a2b4e5f42667-e3434b10c8a69675.journal~:27fdfb0 (of 41943040 bytes, 99%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a2b4e5f42667-e3434b10c8a69675.journal~ (Bad message)
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@e222d28928c9407e8e105b11f7a1a6f7-000000000002fe9a-0005a15dd0785769.journal
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000.journal
4c6e088: Data object references invalid entry at 4cb6eb8
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a67841bf558a-b0b35fd1b32dee20.journal~:4caf0c8 (of 83886080 bytes, 95%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a67841bf558a-b0b35fd1b32dee20.journal~ (Bad message)
000000: Invalid tail monotonic timestamp
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@2692680c53b141bb8efcc4e334c26f01-0000000000000663-00059fefd2b74068.journal:16756f8 (of 25165824 bytes, 93%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@2692680c53b141bb8efcc4e334c26f01-0000000000000663-00059fefd2b74068.journal (Bad message)
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@e4bfd5a9ceac48349a89e707b6c5a706-000000000000066d-0005a2b4e7879a0e.journal
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@00059fefd1183130-0b271e2d4e607e8a.journal~
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a2b4e78ec77c-24e1150011ad73c4.journal~
PASS: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/system@0005a5466435966e-996f477039047062.journal~
8f91e0: Invalid array offset 9d1b68
File corruption detected at /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a67846b1c86f-c98be27940c57207.journal~:9cfe98 (of 16777216 bytes, 61%).
FAIL: /var/log/journal/16fa2990e5014c52bbca62e8a9eb3558/user-1000@0005a67846b1c86f-c98be27940c57207.journal~ (Bad message)How do I safely delete the offending files and repair my system without making my system inoperable?

Once this is fixed, will it help in the future if I limit the log file size to say 50MB?

Code:sudo gedit /etc/systemd/journald.confCode:SystemMaxUse=50M