I just upgraded and realized that my old image has loads and loads of rotated journal logs. This path:
/usr/lib/live/mount/persistence/boot/1.4-rolling-202301192311/rw/var/log/journal/1a84f946b12e401c8186a3283b1235fb
Has these files (plus more, just a sample):
rw-r-----+ 1 root crontab 72M Jan 21 19:39 system@d2c245821d6f4defb1f2d3d1851683fc-0000000000000001-0005f2ab1a29cb18.journal
-rw-r-----+ 1 root crontab 80M Jan 23 08:59 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000178ab-0005f2d12f73d080.journal
-rw-r-----+ 1 root crontab 72M Jan 25 11:27 system@d2c245821d6f4defb1f2d3d1851683fc-000000000002ef0b-0005f2f07b820b7e.journal
-rw-r-----+ 1 root crontab 72M Jan 27 13:52 system@d2c245821d6f4defb1f2d3d1851683fc-0000000000046569-0005f31ac898dc32.journal
-rw-r-----+ 1 root crontab 72M Jan 29 16:55 system@d2c245821d6f4defb1f2d3d1851683fc-000000000005dd58-0005f3450b8efb40.journal
-rw-r-----+ 1 root crontab 72M Jan 31 17:11 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000757c7-0005f36fd495b623.journal
-rw-r-----+ 1 root crontab 80M Feb 2 17:31 system@d2c245821d6f4defb1f2d3d1851683fc-000000000008d7d8-0005f3984a21c5a4.journal
-rw-r-----+ 1 root crontab 80M Feb 4 20:07 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000a5ba0-0005f3c0cc2ecab0.journal
-rw-r-----+ 1 root crontab 80M Feb 6 20:50 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000bdb68-0005f3eb38782ac9.journal
-rw-r-----+ 1 root crontab 72M Feb 8 17:59 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000d5fdd-0005f4140ad7a2eb.journal
-rw-r-----+ 1 root crontab 80M Feb 10 11:19 system@d2c245821d6f4defb1f2d3d1851683fc-00000000000eeb4e-0005f439e6059d27.journal
-rw-r-----+ 1 root crontab 80M Feb 11 10:31 system@d2c245821d6f4defb1f2d3d1851683fc-00000000001076f1-0005f45c8ac26d54.journal
-rw-r-----+ 1 root crontab 72M Feb 13 01:52 system@d2c245821d6f4defb1f2d3d1851683fc-000000000012557c-0005f46ffbd6f995.journal
Can I manually delete these? If I need to revert to this image (which is why I always keep n-1), will systemd have an issue with missing files?