topic eMMC error occurred when saving continuous data in I.MX6 in i.MX Processors https://community.nxp.com/t5/i-MX-Processors/eMMC-error-occurred-when-saving-continuous-data-in-I-MX6/m-p/1358163#M181791 <P><SPAN>Hello, I am currently using the i.mx6 quard.</SPAN></P><P>There is an issue with eMMC errors when saving continuous data in I.MX6.</P><P><SPAN>The storage of eMMC is 8 GB and related log is as follows.</SPAN></P><PRE>EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:<SPAN>755</SPAN>: group <SPAN>0</SPAN><SPAN>, </SPAN>block bitmap <SPAN>and </SPAN>bg descriptor inconsistent: <SPAN>30124 </SPAN>vs <SPAN>30125 </SPAN>free clusters<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>28 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:<SPAN>755</SPAN>: group <SPAN>0</SPAN><SPAN>, </SPAN>block bitmap <SPAN>and </SPAN>bg descriptor inconsistent: <SPAN>30124 </SPAN>vs <SPAN>30125 </SPAN>free clusters<BR /><BR />EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>1413445662</SPAN>: comm cp: lblock <SPAN>50113 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block 246125EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR /><SPAN>1117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />EXT4-fs (mmcblk3p2): pa d648e048: logic <SPAN>0</SPAN><SPAN>, </SPAN>phys. <SPAN>60128</SPAN><SPAN>, </SPAN>len <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>r.crit kernel: EXT4-fs error (devfree <SPAN>18</SPAN><SPAN>, </SPAN>pa_free <SPAN>16<BR /></SPAN>ice mmcblk3p2): ext4_map_blocks:5EXT4-fs (mmcblk3p2): pa d648e0d8: logic <SPAN>32</SPAN><SPAN>, </SPAN>phys. <SPAN>60160</SPAN><SPAN>, </SPAN>len <SPAN>96<BR /></SPAN><SPAN>67</SPAN>: inode #<SPAN>50867</SPAN>: block 141344566EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN><SPAN>2</SPAN>: comm cp: lblock <SPAN>50113 </SPAN>mapped tfree <SPAN>50</SPAN><SPAN>, </SPAN>pa_free <SPAN>32<BR /></SPAN>o illegal pblock (length <SPAN>1</SPAN>)<BR />Sep EXT4-fs (mmcblk3p2): pa d648e168: logic <SPAN>128</SPAN><SPAN>, </SPAN>phys. <SPAN>60416</SPAN><SPAN>, </SPAN>len <SPAN>384<BR /></SPAN><SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>it kernel: EXT4-fs error (device free <SPAN>202</SPAN><SPAN>, </SPAN>pa_free <SPAN>128<BR /></SPAN>mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: EXT4-fs (mmcblk3p2): pa d64cf048: logic <SPAN>49152</SPAN><SPAN>, </SPAN>phys. <SPAN>83968</SPAN><SPAN>, </SPAN>len <SPAN>2048<BR /></SPAN>inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: cEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>2</SPAN><SPAN>, </SPAN>omm cp: lblock <SPAN>50112 </SPAN>mapped to ilfree <SPAN>828</SPAN><SPAN>, </SPAN>pa_free <SPAN>1088<BR /></SPAN>legal pblock (length <SPAN>1</SPAN>)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e048: logic <SPAN>0</SPAN><SPAN>, </SPAN>phys. <SPAN>60128</SPAN><SPAN>, </SPAN>len <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>18</SPAN><SPAN>, </SPAN>pa_free <SPAN>16<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e0d8: logic <SPAN>32</SPAN><SPAN>, </SPAN>phys. <SPAN>60160</SPAN><SPAN>, </SPAN>len <SPAN>96<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>50</SPAN><SPAN>, </SPAN>pa_free <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e168: logic <SPAN>128</SPAN><SPAN>, </SPAN>phys. <SPAN>60416</SPAN><SPAN>, </SPAN>len <SPAN>384<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>202</SPAN><SPAN>, </SPAN>pa_free <SPAN>128<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d64cf048: logic <SPAN>49152</SPAN><SPAN>, </SPAN>phys. <SPAN>83968</SPAN><SPAN>, </SPAN>len <SPAN>2048<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>2</SPAN><SPAN>, </SPAN>free <SPAN>828</SPAN><SPAN>, </SPAN>pa_free <SPAN>1088<BR /></SPAN><SPAN><BR /></SPAN>EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:<SPAN>1845</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm cp: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>55 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:<SPAN>1845</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm cp: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>58 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>59 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>r.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox cron.info crond[<SPAN>549</SPAN>]: (root) WRONG FILE OWNER (/etc/crontab)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox cron.info crond[<SPAN>549</SPAN>]: (root) WRONG FILE OWNER (/var/spool/cron/root)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12</SPAN></PRE><P>&nbsp;</P><P>Examples of such symptoms are as follows.</P><OL><LI>Transmit an avi file with a size of 200MB by LAN communication through scp.</LI><LI>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...).</LI><LI>Sending 1.avi after booting and sending 2.avi after rebooting is no problem.</LI><LI>Sending 1.avi after booting and overwriting 1.avi again is no problem.</LI></OL><P>Conclusion: The problem always only occurs if I save the data with different names more than once without rebooting.</P><P>&nbsp;</P><P>What should i do?</P><P>Please help me!</P> Wed, 20 Oct 2021 00:51:22 GMT MrHoon89 2021-10-20T00:51:22Z eMMC error occurred when saving continuous data in I.MX6 https://community.nxp.com/t5/i-MX-Processors/eMMC-error-occurred-when-saving-continuous-data-in-I-MX6/m-p/1358163#M181791 <P><SPAN>Hello, I am currently using the i.mx6 quard.</SPAN></P><P>There is an issue with eMMC errors when saving continuous data in I.MX6.</P><P><SPAN>The storage of eMMC is 8 GB and related log is as follows.</SPAN></P><PRE>EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:<SPAN>755</SPAN>: group <SPAN>0</SPAN><SPAN>, </SPAN>block bitmap <SPAN>and </SPAN>bg descriptor inconsistent: <SPAN>30124 </SPAN>vs <SPAN>30125 </SPAN>free clusters<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>28 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_generate_buddy:<SPAN>755</SPAN>: group <SPAN>0</SPAN><SPAN>, </SPAN>block bitmap <SPAN>and </SPAN>bg descriptor inconsistent: <SPAN>30124 </SPAN>vs <SPAN>30125 </SPAN>free clusters<BR /><BR />EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>1413445662</SPAN>: comm cp: lblock <SPAN>50113 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block 246125EXT4-fs error (device mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR /><SPAN>1117</SPAN>: comm cp: lblock <SPAN>50112 </SPAN>mapped to illegal pblock (length <SPAN>1</SPAN>)<BR />EXT4-fs (mmcblk3p2): pa d648e048: logic <SPAN>0</SPAN><SPAN>, </SPAN>phys. <SPAN>60128</SPAN><SPAN>, </SPAN>len <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>r.crit kernel: EXT4-fs error (devfree <SPAN>18</SPAN><SPAN>, </SPAN>pa_free <SPAN>16<BR /></SPAN>ice mmcblk3p2): ext4_map_blocks:5EXT4-fs (mmcblk3p2): pa d648e0d8: logic <SPAN>32</SPAN><SPAN>, </SPAN>phys. <SPAN>60160</SPAN><SPAN>, </SPAN>len <SPAN>96<BR /></SPAN><SPAN>67</SPAN>: inode #<SPAN>50867</SPAN>: block 141344566EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN><SPAN>2</SPAN>: comm cp: lblock <SPAN>50113 </SPAN>mapped tfree <SPAN>50</SPAN><SPAN>, </SPAN>pa_free <SPAN>32<BR /></SPAN>o illegal pblock (length <SPAN>1</SPAN>)<BR />Sep EXT4-fs (mmcblk3p2): pa d648e168: logic <SPAN>128</SPAN><SPAN>, </SPAN>phys. <SPAN>60416</SPAN><SPAN>, </SPAN>len <SPAN>384<BR /></SPAN><SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>it kernel: EXT4-fs error (device free <SPAN>202</SPAN><SPAN>, </SPAN>pa_free <SPAN>128<BR /></SPAN>mmcblk3p2): ext4_map_blocks:<SPAN>567</SPAN>: EXT4-fs (mmcblk3p2): pa d64cf048: logic <SPAN>49152</SPAN><SPAN>, </SPAN>phys. <SPAN>83968</SPAN><SPAN>, </SPAN>len <SPAN>2048<BR /></SPAN>inode #<SPAN>50867</SPAN>: block <SPAN>2461251117</SPAN>: cEXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>2</SPAN><SPAN>, </SPAN>omm cp: lblock <SPAN>50112 </SPAN>mapped to ilfree <SPAN>828</SPAN><SPAN>, </SPAN>pa_free <SPAN>1088<BR /></SPAN>legal pblock (length <SPAN>1</SPAN>)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e048: logic <SPAN>0</SPAN><SPAN>, </SPAN>phys. <SPAN>60128</SPAN><SPAN>, </SPAN>len <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>18</SPAN><SPAN>, </SPAN>pa_free <SPAN>16<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e0d8: logic <SPAN>32</SPAN><SPAN>, </SPAN>phys. <SPAN>60160</SPAN><SPAN>, </SPAN>len <SPAN>96<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>50</SPAN><SPAN>, </SPAN>pa_free <SPAN>32<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d648e168: logic <SPAN>128</SPAN><SPAN>, </SPAN>phys. <SPAN>60416</SPAN><SPAN>, </SPAN>len <SPAN>384<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>1</SPAN><SPAN>, </SPAN>free <SPAN>202</SPAN><SPAN>, </SPAN>pa_free <SPAN>128<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs (mmcblk3p2): pa d64cf048: logic <SPAN>49152</SPAN><SPAN>, </SPAN>phys. <SPAN>83968</SPAN><SPAN>, </SPAN>len <SPAN>2048<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>39 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_mb_release_inode_pa:<SPAN>3812</SPAN>: group <SPAN>2</SPAN><SPAN>, </SPAN>free <SPAN>828</SPAN><SPAN>, </SPAN>pa_free <SPAN>1088<BR /></SPAN><SPAN><BR /></SPAN>EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:<SPAN>1845</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm cp: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>55 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): ext4_find_dest_de:<SPAN>1845</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm cp: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>58 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>22</SPAN>:<SPAN>59 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>48770</SPAN>: block <SPAN>221185</SPAN>: comm ls: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1909753701</SPAN><SPAN>, </SPAN>rec_len=<SPAN>31385</SPAN><SPAN>, </SPAN>name_len=<SPAN>142<BR /></SPAN>EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox useEXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>r.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12<BR /></SPAN>Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox cron.info crond[<SPAN>549</SPAN>]: (root) WRONG FILE OWNER (/etc/crontab)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox cron.info crond[<SPAN>549</SPAN>]: (root) WRONG FILE OWNER (/var/spool/cron/root)<BR />Sep <SPAN>5 23</SPAN>:<SPAN>23</SPAN>:<SPAN>01 </SPAN>imx6qpdlsolox user.crit kernel: EXT4-fs error (device mmcblk3p2): htree_dirblock_to_tree:<SPAN>987</SPAN>: inode #<SPAN>90229</SPAN>: block <SPAN>387484</SPAN>: comm crond: bad entry in directory: rec_len % <SPAN>4 </SPAN>!= <SPAN>0 </SPAN>- offset=<SPAN>0</SPAN>(<SPAN>0</SPAN>)<SPAN>, </SPAN>inode=<SPAN>1393129371</SPAN><SPAN>, </SPAN>rec_len=<SPAN>42527</SPAN><SPAN>, </SPAN>name_len=<SPAN>12</SPAN></PRE><P>&nbsp;</P><P>Examples of such symptoms are as follows.</P><OL><LI>Transmit an avi file with a size of 200MB by LAN communication through scp.</LI><LI>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...).</LI><LI>Sending 1.avi after booting and sending 2.avi after rebooting is no problem.</LI><LI>Sending 1.avi after booting and overwriting 1.avi again is no problem.</LI></OL><P>Conclusion: The problem always only occurs if I save the data with different names more than once without rebooting.</P><P>&nbsp;</P><P>What should i do?</P><P>Please help me!</P> Wed, 20 Oct 2021 00:51:22 GMT https://community.nxp.com/t5/i-MX-Processors/eMMC-error-occurred-when-saving-continuous-data-in-I-MX6/m-p/1358163#M181791 MrHoon89 2021-10-20T00:51:22Z