Comment 49 for bug 1423672

FYI, the same errors happened to me on real hardware (a Raspberry Pi 2 B), based on a custom Debian Jessie image.

The image uses a ext2 filesystem created on a x86 Boot2docker host (Kernel "Linux fbd0c1340061 4.1.12-boot2docker #1 SMP Tue Nov 3 06:03:36 UTC 2015 x86_64 GNU/Linux").

While remounting the filesystem as r-w on the Raspberry and writing to it I got:

[53406.370524] EXT4-fs (mmcblk0p3): mounting ext2 file system using the ext4 subsystem
[53406.575883] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: (null)
[53416.394833] EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:757: group 1, block bitmap and bg descriptor inconsistent: 8953 vs 8990 free clusters
[53435.245967] EXT4-fs error (device mmcblk0p3): ext4_lookup:1417: inode #2: comm rsync: deleted inode referenced: 46849
[53481.805006] EXT4-fs error (device mmcblk0p3): ext4_lookup:1417: inode #2: comm ls: deleted inode referenced: 46849

The Raspi isn't running the most current Kernel yet (it's "Linux intermodul 3.19.3-v7 #1 SMP PREEMPT Mon Nov 30 08:37:00 UTC 2015 armv7l GNU/Linux"), but perhaps this helps analyzing this bug as it's not a VM...