On Wed, 22 Apr 2015 00:28:12 +0200 Michał Zegan <webczat_...@poczta.onet.pl> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello. > > I have just removed my journal files and restarted journald. I then > generated sealing keys, saved the verification key. The system worked > for maybe an hour or less, I had to power it off, then it was > restarted. I tried to verify the journal. > This is what happened: > > PASS: /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/system.journal > > > 390398: tag failed verification > > > File corruption detected at > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1000.journal:3903 > 98 > (of 8388608 bytes, 44%). > FAIL: > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1000.journal > (Bad message) > > 3987a0: tag failed verification > > > File corruption detected at > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1002.journal:3987 > a0 > (of 8388608 bytes, 44%). > FAIL: > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1002.journal > (Bad message) > > 3903a0: tag failed verification > > > File corruption detected at > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1001.journal:3903 > a0 > (of 8388608 bytes, 44%). > FAIL: > /var/log/journal/a523e1ef5ffe4b15b9d2698b85e944cd/user-1001.journal > (Bad message) > > What is happening here? It always happens after sealing, no matter > what I am doing, all new journal files are corrupted and show this > message. > > Systemd version 219, system is archlinux, kernel 3.19.3-3-ARCH, and > filesystem is btrfs if at all important. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBAgAGBQJVNs77AAoJEHb1CzgxXKwYldcP/jGnuCyN1hcQvUHgc4ZS+CkW > gCEf59TteLYO/7yVQnrAs4gHFJ6WJlFw8+2L1Lt9gpts2h41oQxyPjhfa6578kSB > 2ZC+9McpjLqMctn+hBt3GcPyi/vpr7QAm29sBoPpbCl8hCQQeRbGg5dfUnV0q7ot > ueXiO2VMW2wYDz3/0gmqCf7Fh+ChWdBTNAZFrTMqP1hLw0xTukazpNFGm8sStgcp > TC2p3JlLmmdCXHxPTGnxFj4jVWuYIOzDajh5GZUPlhmlBy48TKSzF+T3ri6zkOr5 > +lyDC1fho5P7shdSN07OlGLSeg6JXC193gBB8WEhUwTs29fZzjyChke0dHVq/WSj > 2pYpSr5cncxiUnwR5HTAhBRKHctKP8/5Rqmgu9GCEpy52mtuDsHUQQVbckjMaOYj > 9Bz1y+pLNVi5v9AeD3wv/TnxEKeIYd4lwfs9pSutrF/KDo3XxPzys+jgbQvDrxVn > zbiKW9X8gc0r6P9qQ5p1jcBndW3dstQExNqGSZCgrCckymDxiSzfhjKQe8G/rD/O > 29By4j9vbhHRq/gVpo0MWdnn8I1PCAxpqrftxCLmkEUNCgNAn+xIzwe+G6ppmAv7 > 4ZnbYfvLAz4Fj0g4QmswCXZB+DEqowrHK5N89BWxRSiY19A87l7BeFDzIFytOfkC > LHhedmjVTZXNvgTZXyeE > =VsvH > -----END PGP SIGNATURE----- > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel It seems you have exactly the same issue that I had. I described the problem here: http://lists.freedesktop.org/archives/systemd-devel/2015-February/028119.html , but no one answered it. I was just testing this sealing feature and forgot about it because I couldn't make it work, and there was no info what to do with the problem. It seems I'm not the only one who has the issue, you have it on archlinux, and I had it on debian, different kernels, and different filesystem types.
pgp4xXrSZvggC.pgp
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
