Re: [systemd-devel] Failed to get journal fields: Bad message

2017-02-28 Thread Krzysztof Błaszkowski
Lennart, On Mon, 2017-02-27 at 19:42 +0100, Lennart Poettering wrote: > On Mon, 27.02.17 08:29, Krzysztof Błaszkowski (k...@sysmikro.com.pl) > wrote: > > > > > > > > > The journal file format is primarily an append-based format > > > (though > > > some fields at the front are updated, to link t

Re: [systemd-devel] Failed to get journal fields: Bad message

2017-02-27 Thread Lennart Poettering
On Mon, 27.02.17 08:29, Krzysztof Błaszkowski (k...@sysmikro.com.pl) wrote: > > The journal file format is primarily an append-based format (though > > some fields at the front are updated, to link the new additions > > up). This makes it not too bad when it comes to disk corruptions, and > > data

Re: [systemd-devel] Failed to get journal fields: Bad message

2017-02-26 Thread Krzysztof Błaszkowski
On Sun, 2017-02-26 at 21:45 +0100, Lennart Poettering wrote: > On Sat, 25.02.17 11:10, Krzysztof Błaszkowski (k...@sysmikro.com.pl) > wrote: > > > > > > > Any thoughts ? wise only .. > > > > when there was /var/log/messages available there was no problem > > with > > accessing logs because th

Re: [systemd-devel] Failed to get journal fields: Bad message

2017-02-26 Thread Lennart Poettering
On Sat, 25.02.17 11:10, Krzysztof Błaszkowski (k...@sysmikro.com.pl) wrote: > > Any thoughts ? wise only .. > > when there was /var/log/messages available there was no problem with > accessing logs because the "database" was plain text but now. > > corrupted less or more it did not matter. it i

[systemd-devel] Failed to get journal fields: Bad message

2017-02-25 Thread Krzysztof Błaszkowski
Any thoughts ? wise only .. when there was /var/log/messages available there was no problem with accessing logs because the "database" was plain text but now. corrupted less or more it did not matter. it is responsibility of /var/log filesystem to perform right recovery .. I want to see what co