On 02/27/2014 08:56 AM, Adam Williamson wrote:
On Thu, 2014-02-27 at 08:25 +0100, Ralf Corsepius wrote:
On 02/27/2014 08:08 AM, Adam Williamson wrote:
On Thu, 2014-02-27 at 07:10 +0100, Ralf Corsepius wrote:
On 02/27/2014 06:43 AM, Chris Murphy wrote:
On Feb 26, 2014, at 9:24 AM, Neal Becker
On Thu, 2014-02-27 at 08:25 +0100, Ralf Corsepius wrote:
> On 02/27/2014 08:08 AM, Adam Williamson wrote:
> > On Thu, 2014-02-27 at 07:10 +0100, Ralf Corsepius wrote:
> >> On 02/27/2014 06:43 AM, Chris Murphy wrote:
> >>>
> >>> On Feb 26, 2014, at 9:24 AM, Neal Becker wrote:
> >>>
> sudo jour
On 02/27/2014 08:08 AM, Adam Williamson wrote:
On Thu, 2014-02-27 at 07:10 +0100, Ralf Corsepius wrote:
On 02/27/2014 06:43 AM, Chris Murphy wrote:
On Feb 26, 2014, at 9:24 AM, Neal Becker wrote:
sudo journalctl --verify
all say 'PASS'
OK good news. It looks like some sort of throttling b
On Thu, 2014-02-27 at 07:10 +0100, Ralf Corsepius wrote:
> On 02/27/2014 06:43 AM, Chris Murphy wrote:
> >
> > On Feb 26, 2014, at 9:24 AM, Neal Becker wrote:
> >
> >> sudo journalctl --verify
> >> all say 'PASS'
> >
> > OK good news. It looks like some sort of throttling by rsyslogd. I'm
> > vag
On 02/27/2014 06:43 AM, Chris Murphy wrote:
On Feb 26, 2014, at 9:24 AM, Neal Becker wrote:
sudo journalctl --verify
all say 'PASS'
OK good news. It looks like some sort of throttling by rsyslogd. I'm vaguely
curious if it's some runaway/annoyed process is dumping a lot of message into
th
On Feb 26, 2014, at 9:24 AM, Neal Becker wrote:
> sudo journalctl --verify
> all say 'PASS'
OK good news. It looks like some sort of throttling by rsyslogd. I'm vaguely
curious if it's some runaway/annoyed process is dumping a lot of message into
the journal, and whether the journal can keep
Chris Murphy wrote:
>
> On Feb 25, 2014, at 12:45 PM, Neal Becker wrote:
>
>> Running on btrfs (hopefully that doesn't matter)
>
> If you haven't set xattr +C on /var/log/journal, then if you get a chance I'd
> be curious to see the results from:
>
> journalctl --verify
>
> btrfs scrub start
On Feb 25, 2014, at 9:54 PM, Chris Murphy wrote:
>
> Since I'm using xattr +C on /var/log/journal at the moment, the logs don't
> have Btrfs checksums, so I don't have an independent way to know if the logs
> are corrupt at a file system level or just internally.
journalctl --verify and Btrfs
On Feb 25, 2014, at 12:45 PM, Neal Becker wrote:
> Running on btrfs (hopefully that doesn't matter)
If you haven't set xattr +C on /var/log/journal, then if you get a chance I'd
be curious to see the results from:
journalctl --verify
btrfs scrub start -BR /
Depending on the size of the Btrf
On 02/25/2014 01:44 PM, Neal Becker wrote:
> OK, I think there is no question that time did not go back in
> /var/log/messages.
> Actually, the messages are scrambled.
>
> First it is Jan 25. Then it it Jan 8. We go through normal looking periods
> of
> Jan 9 and 10, and Jan 13 before we're
Neal Becker wrote:
> OK, I think there is no question that time did not go back in
> /var/log/messages. Actually, the messages are scrambled.
>
> First it is Jan 25. Then it it Jan 8. We go through normal looking periods
> of
> Jan 9 and 10, and Jan 13 before we're back on Feb 25. I don't thin
OK, I think there is no question that time did not go back in
/var/log/messages.
Actually, the messages are scrambled.
First it is Jan 25. Then it it Jan 8. We go through normal looking periods of
Jan 9 and 10, and Jan 13 before we're back on Feb 25. I don't think this can
be
explained by
12 matches
Mail list logo
