same ext4 corruption in multiple systems

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1273776

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Sorry but i can't boot the system or chroot into it.

and i've found this in syslog:

Jan 24 23:00:02 ay5 kernel: [371845.888834] EXT4-fs error (device sda2): ext4_iget:3888: inode #127236: comm python-d: bad extra_isize (65663 != 256)
Jan 24 23:00:02 ay5 kernel: [371845.888849] Aborting journal on device sda2-8.
Jan 24 23:00:02 ay5 kernel: [371845.890819] EXT4-fs (sda2): Remounting filesystem read-only
Jan 24 23:00:02 ay5 kernel: [371845.902919] EXT4-fs error (device sda2): ext4_iget:3888: inode #127236: comm python-d: bad extra_isize (65663 != 256)

Can you add the v option to tar to get verbose output, so it would be tar -cvf

Also, have you been able to tar up that directory in the past? Did this just start happening after a recent update or upgrade?

Sorry maybe it was not clear, my fault. I can't boot the dom disk with problems so i've attached it to another system and mounted it in ~/a/m. I've run the tar command on the whole mounted partition (~/a/m -> / on faulted disk). If you think you still need tar -cvf i can provide it, please tell me. I've never tried to tar that directory but it's not a tar problem. I can't access some files/directories on this partition because the ext4 filesystem is ruined. I always used this kernel so i don't know if it was working on previous versions. I'm also not able to test because i'm not able to replicate the problem. I can only wait for angry clients :)