<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic UBIFS do_writepage error in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-do-writepage-error/m-p/1573408#M199105</link>
    <description>&lt;P&gt;Dear sir,&lt;/P&gt;&lt;P&gt;I'm using an i.mx6ull (SDK 2.0.0) with a NAND flash.&lt;/P&gt;&lt;P&gt;But, &lt;SPAN&gt;The following error occurs only on certain boards, and the file system is changed to read only. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It will be recovered upon reboot, but the same phenomenon will be repeated soon. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What's the cause?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 6): ubifs_scan: corrupt empty space at LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: corruption at LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: first 8192 bytes from LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scan: LEB 1718 scanning failed&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 2363 bytes in jhead 2, error -117&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5304 of inode 37836, error -117&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5315 of inode 37836, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1199 bytes in jhead 2, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5316 of inode 37836, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1262 bytes in jhead 2, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5317 of inode 37836, error -30&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sungkyun Ko&lt;/P&gt;</description>
    <pubDate>Fri, 23 Dec 2022 07:26:19 GMT</pubDate>
    <dc:creator>Sungkyun</dc:creator>
    <dc:date>2022-12-23T07:26:19Z</dc:date>
    <item>
      <title>UBIFS do_writepage error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-do-writepage-error/m-p/1573408#M199105</link>
      <description>&lt;P&gt;Dear sir,&lt;/P&gt;&lt;P&gt;I'm using an i.mx6ull (SDK 2.0.0) with a NAND flash.&lt;/P&gt;&lt;P&gt;But, &lt;SPAN&gt;The following error occurs only on certain boards, and the file system is changed to read only. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It will be recovered upon reboot, but the same phenomenon will be repeated soon. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What's the cause?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 6): ubifs_scan: corrupt empty space at LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: corruption at LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: first 8192 bytes from LEB 1718:112454&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): ubifs_scan: LEB 1718 scanning failed&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 2363 bytes in jhead 2, error -117&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5304 of inode 37836, error -117&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5315 of inode 37836, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1199 bytes in jhead 2, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5316 of inode 37836, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1262 bytes in jhead 2, error -30&lt;BR /&gt;UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5317 of inode 37836, error -30&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sungkyun Ko&lt;/P&gt;</description>
      <pubDate>Fri, 23 Dec 2022 07:26:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-do-writepage-error/m-p/1573408#M199105</guid>
      <dc:creator>Sungkyun</dc:creator>
      <dc:date>2022-12-23T07:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: UBIFS do_writepage error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-do-writepage-error/m-p/1576494#M199421</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/188268"&gt;@Sungkyun&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This UBIFS error is reported many times, for certain reasons like the NAND driver or the HW is buggy. &lt;BR /&gt;When the flash regions have been erased but have never been written, UBIFS expects to see all 0xFFs there, and if it doesn't, it reports about corrupt space.&lt;/P&gt;
&lt;P&gt;There is a possibility to switch to read-only mode to prevent further corruption due to corrupt space error.&lt;/P&gt;
&lt;P&gt;For further debugging of the issue, we would recommend you get in touch with the MDT community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;Dhruvit.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 10:02:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-do-writepage-error/m-p/1576494#M199421</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2023-01-03T10:02:45Z</dc:date>
    </item>
  </channel>
</rss>

