** Summary changed:
- ext4 turned read-only following a cronjob run
+ ext4 turned read-only during logrotate daily run
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1423672
Title:
ext4
This occurred on another VM. I guess I will have to roll our the 4.0-rc2
kernel everywhere.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1423672
Title:
ext4 turned read-only during log
It would be good to know if v4.0-rc2 fixes this. If it does, we can
look at the git logs to see what may be the fix, or perform a "Reverse"
bisect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Also, did this issue start happening after an update/upgrade? Was there
a prior kernel version where you were not having this particular
problem? This will help determine if the problem you are seeing is the
result of a regression, and when this regression was introduced. If
this is a regression,
The first occurrence of this problem goes back to Feb 17th. While I keep
all the VMs up to date on a daily basis, I now have doubts about the
hypervisor's RAM (not ECC by the way). I brought all the VMs offline to
have their FSes checked (all ext4). Several of them needed fixing by
fsck. Since they
This happened to me here as well. Also in a VM.
[ 42.042806] [ cut here ]
[ 42.042812] WARNING: CPU: 0 PID: 617 at
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
[ 42.042813] Modules linked in: kvm_intel kvm cirrus snd
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
--
You recei
FWIW, I've seen this happen, too, basically since I upgraded to Trusty,
I believe. Only ever happens on VMs, never on physical machines. All my
virtual disks use Virtio, cache mode 'none' (yeah, I know), I/O mode
'native', with raw LVM volumes as backend.
--
You received this bug notification be
It's been a while since there was any activity on this bug. Does this
issues still happen with the latest updates?
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notificat
Indeed I haven't seen this error in a few weeks, the last time was maybe
around six-eight weeks ago. But we all know how absence of evidence
isn't evidence of absence :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Things seem to have stabilized recently as the last occurrence I
witnessed was on May 13th.
I searched all my 2014 and 2015 logs for "ext4_mb_generate_buddy" and
here is what I got:
Nov 24 02:54:03 smb kernel: [842091.081319] EXT4-fs error (device vda1):
ext4_mb_generate_buddy:756: group 1, bloc
No, it isn't gone after all, it just happened again:
Jun 13 15:20:37 oberon kernel: [117379.592167] EXT4-fs error (device dm-1):
ext4_mb_generate_buddy:756: group 1, block bitmap and bg descriptor
inconsistent: 19382 vs 19381 free clusters
Jun 13 15:20:37 oberon kernel: [117379.592903] Aborting
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Confirmed
** Summary changed:
- ext4 turned read-only during logrotate daily run
+ ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor
inconsistent: X vs Y
--
You received this bug notification because you are a
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
On 03/09/2015 04:18 PM, Oliver Brakmann wrote:
> Only ever happens on VMs, never on physical machines. All my
> virtual disks use Virtio, cache mode 'none' (yeah, I know), I/O mode
> 'native', with raw LVM volumes as backend.
Exact same setup here. What's wrong with cache mode set to none? This
a
15 matches
Mail list logo
