eMMC error occurred when saving continuous data in I.MX6

[MrHoon89]

Hello, I am currently using the i.mx6 quard.

There is an issue with eMMC errors when saving continuous data in I.MX6.

The storage of eMMC is 8 GB and related log is as follows.

EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:755: group 0, block bitmap and bg descriptor inconsistent: 30124 vs 30125 free clusters
Sep  5 23:22:28 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:755: group 0, block bitmap and bg descriptor inconsistent: 30124 vs 30125 free clusters

EXT4-fs error (device mmcblk3p2): ext4_map_blocks:567: inode #50867: block 2461251117: comm cp: lblock 50112 mapped to illegal pblock (length 1)
EXT4-fs error (device mmcblk3p2): ext4_map_blocks:567: inode #50867: block 1413445662: comm cp: lblock 50113 mapped to illegal pblock (length 1)
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_map_blocks:567: inode #50867: block 246125EXT4-fs error (device mmcblk3p2): ext4_map_blocks:567: inode #50867: block 2461251117: comm cp: lblock 50112 mapped to illegal pblock (length 1)
1117: comm cp: lblock 50112 mapped to illegal pblock (length 1)
EXT4-fs (mmcblk3p2): pa d648e048: logic 0, phys. 60128, len 32
Sep  5 23:22:39 imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, r.crit kernel: EXT4-fs error (devfree 18, pa_free 16
ice mmcblk3p2): ext4_map_blocks:5EXT4-fs (mmcblk3p2): pa d648e0d8: logic 32, phys. 60160, len 96
67: inode #50867: block 141344566EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, 2: comm cp: lblock 50113 mapped tfree 50, pa_free 32
o illegal pblock (length 1)
Sep EXT4-fs (mmcblk3p2): pa d648e168: logic 128, phys. 60416, len 384
5 23:22:39 imx6qpdlsolox user.crEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, it kernel: EXT4-fs error (device free 202, pa_free 128
mmcblk3p2): ext4_map_blocks:567: EXT4-fs (mmcblk3p2): pa d64cf048: logic 49152, phys. 83968, len 2048
inode #50867: block 2461251117: cEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 2, omm cp: lblock 50112 mapped to ilfree 828, pa_free 1088
legal pblock (length 1)
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e048: logic 0, phys. 60128, len 32
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, free 18, pa_free 16
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e0d8: logic 32, phys. 60160, len 96
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, free 50, pa_free 32
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e168: logic 128, phys. 60416, len 384
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 1, free 202, pa_free 128
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d64cf048: logic 49152, phys. 83968, len 2048
Sep  5 23:22:39 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:3812: group 2, free 828, pa_free 1088

EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:1845: inode #48770: block 221185: comm cp: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
Sep  5 23:22:55 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:1845: inode #48770: block 221185: comm cp: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #48770: block 221185: comm ls: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
Sep  5 23:22:58 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #48770: block 221185: comm ls: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #48770: block 221185: comm ls: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
Sep  5 23:22:59 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #48770: block 221185: comm ls: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1909753701, rec_len=31385, name_len=142
EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #90229: block 387484: comm crond: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1393129371, rec_len=42527, name_len=12
Sep  5 23:23:01 imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #90229: block 387484: comm crond: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1393129371, rec_len=42527, name_len=12
r.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #90229: block 387484: comm crond: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1393129371, rec_len=42527, name_len=12
Sep  5 23:23:01 imx6qpdlsolox cron.info crond[549]: (root) WRONG FILE OWNER (/etc/crontab)
Sep  5 23:23:01 imx6qpdlsolox cron.info crond[549]: (root) WRONG FILE OWNER (/var/spool/cron/root)
Sep  5 23:23:01 imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:987: inode #90229: block 387484: comm crond: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1393129371, rec_len=42527, name_len=12

Examples of such symptoms are as follows.

1. Transmit an avi file with a size of 200MB by LAN communication through scp.
2. Sending 1.avi in the initial stage after booting is no problem, but the problem appears when sending to another name (2.avi, 3.avi...).
3. Sending 1.avi after booting and sending 2.avi after rebooting is no problem.
4. Sending 1.avi after booting and overwriting 1.avi again is no problem.

Conclusion: The problem always only occurs if I save the data with different names more than once without rebooting.

What should i do?

Please help me!