Ubuntu
linux package

  1. Trusty (14.04)
  2. Bug #1423672
  3. Comment #20

Comment 20 for bug 1423672

Revision history for this message
Simon Déziel (sdeziel) wrote : Re: [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

On 03/04/2015 05:07 PM, Simon Déziel wrote:
> Before loosing anyone's time on this issue, I'll first make sure the
> hypervisor's RAM is sane. So I'll get back after some memtest86+ then
> I'll look at the 4.0 kernel.

After 15+ hours of memtest86+ (8 full passes), I don't think the RAM is
at fault. I ran a fsck on every VMs and many of them had issues. I'm
still using the default Ubuntu kernel for now.

One weird thing I noticed is that apparently all the affected VMs have
trouble with the /etc/cron.daily/logrotate job:

 error: error creating output file /var/log/syslog.1.gz: File exists
 run-parts: /etc/cron.daily/logrotate exited with return code 1

On those, there was a very old /var/log/syslog.1 and a more recent .1.gz
one too. I removed both and will see if it helps.