https://bugzilla.kernel.org/show_bug.cgi?id=89621 Bug ID: 89621 Summary: EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32 Product: File System Version: 2.5 Kernel Version: 3.16 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext4 Assignee: fs_ext4@xxxxxxxxxxxxxxxxxxxx Reporter: john@xxxxxxxxx Regression: No I've been getting this EXT4 error (on an ext3 filesystem) on two virtual machines, running Debian kernel 3.16-0.bpo.2-amd64. The stack is: Host (3.16): Mdadm raid1 LVM Guest (also 3.16): LVM2 volume, ext3 formatted [ 7.413209] EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem [ 7.431191] EXT4-fs (dm-4): warning: maximal mount count reached, running e2fsck is recommended [ 7.442501] EXT4-fs (dm-4): mounted filesystem with journalled data mode. Opts: data=journal,errors=remount-ro ... [957229.875900] EXT4-fs (dm-4): pa ffff88001f7ff980: logic 0, phys. 9176576, len 128 [957229.878640] EXT4-fs error (device dm-4): ext4_mb_release_inode_pa:3773: group 280, free 128, pa_free 127 [957229.881350] Aborting journal on device dm-4-8. [957229.891273] EXT4-fs (dm-4): Remounting filesystem read-only [957561.369731] EXT4-fs (dm-4): pa ffff880009f7b028: logic 0, phys. 9192448, len 512 [957561.371926] EXT4-fs error (device dm-4): ext4_mb_release_inode_pa:3773: group 280, free 512, pa_free 511 [957688.608554] EXT4-fs error (device dm-4): ext4_put_super:792: Couldn't clean up the journal This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772848 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
