We've encountered a problem with host filesystem (twice with 2.6.32-29 on one system and 4 times with 2.6.32-30 on another one):
EXT4-fs error (device md0): ext4_ext_search_left: inode #27526386: (comm kvm) ix (4064983) != EXT_FIRST_INDEX (0) (depth 1)!
We've encountered it during copying/unpacking large tarball (~0,7G) inside VM (Win 2k8r2).
It looks like redhat's bug 873201, but our filesystem was not shrinked.
Today I'm trying to reproduce this bug on test system (with 2.6.32-31), but unsuccessfully.
Redhat's changelog for kernel shows no changes in ext4 made last month, so I don't think that problem is fixed in 2.6.32-31. All systems were installed as Debian 7.5 and then upgraded to Proxmox 3.2.
Any ideas?
EXT4-fs error (device md0): ext4_ext_search_left: inode #27526386: (comm kvm) ix (4064983) != EXT_FIRST_INDEX (0) (depth 1)!
We've encountered it during copying/unpacking large tarball (~0,7G) inside VM (Win 2k8r2).
It looks like redhat's bug 873201, but our filesystem was not shrinked.
Today I'm trying to reproduce this bug on test system (with 2.6.32-31), but unsuccessfully.
Redhat's changelog for kernel shows no changes in ext4 made last month, so I don't think that problem is fixed in 2.6.32-31. All systems were installed as Debian 7.5 and then upgraded to Proxmox 3.2.
Any ideas?