Hi, on a quite new machine, with ECC memory, stress-tested before installing, installed about a month ago, everything was fine, running squeeze (linux-image-2.6.32-5-openvz-amd64)
I upgraded the kernel to the latest release (2.6.32-41) and apart from the load average being wrong in some VEs, seemed to work quite well. But this week-end I had twice something like: Feb 5 14:05:40 virtual kernel: [408480.738756] EXT4-fs error (device dm-5): ext4_lookup: deleted inode referenced: 11152211 Feb 5 14:05:40 virtual kernel: [408480.738793] Aborting journal on device dm-5-8. Feb 5 14:05:40 virtual kernel: [408480.779450] EXT4-fs (dm-5): Remounting filesystem read-only Feb 5 14:05:40 virtual kernel: [408480.850473] EXT4-fs error (device dm-5): ext4_lookup: deleted inode referenced: 11152219 Feb 5 14:05:40 virtual kernel: [408480.852522] EXT4-fs error (device dm-5): ext4_lookup: deleted inode referenced: 11152212 Feb 5 14:06:19 virtual kernel: [408519.740348] EXT4-fs error (device dm-5): ext4_lookup: deleted inode referenced: 11152220 Unmounting, then running fsck.ext4 -f on the raw device only gave a few deleted inodes warnings. Running a second time did not show any problem. The 104 VZ is on a specific LV, filesystem ext4, in a VG which is on a RAID10 (4 disks) md array. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120206085348.ga26...@alphanet.ch
