<?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 ReadOnly FS in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-ReadOnly-FS/m-p/982523#M145944</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using iMx6ULL in our design with Toshiba NAND. When run my application more than a day , i m getting below errors,&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 22611): ubifs_scan: corrupt empty space at LEB 1565:81920&lt;BR /&gt;UBIFS error (ubi0:0 pid 22611): ubifs_scanned_corruption: corruption at LEB 1565:81920&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): ubifs_scanned_corruption: first 8192 bytes from LEB 1565:81920&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): ubifs_scan: LEB 1565 scanning failed&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): do_commit: commit failed, error -117&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS warning (ubi0:0 pid 22611): ubifs_ro_mode: switched to read-only mode, error -117&lt;BR /&gt;[2020-02-15 21:56:27] CPU: 0 PID: 22611 Comm: sync Not tainted 4.1.15 #1&lt;BR /&gt;[2020-02-15 21:56:27] Hardware name: Freescale i.MX6 UL/ULL (Device Tree)&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80015a78&amp;gt;] from [&amp;lt;80012658&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80012658&amp;gt;] from [&amp;lt;8067b558&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;8067b558&amp;gt;] from [&amp;lt;80226e04&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80226e04&amp;gt;] from [&amp;lt;802173b4&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;802173b4&amp;gt;] from [&amp;lt;800eb5c0&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;800eb5c0&amp;gt;] from [&amp;lt;801110dc&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;801110dc&amp;gt;] from [&amp;lt;8000f400&amp;gt;]&lt;/P&gt;&lt;P&gt;I/O error : Read-only file system&lt;/P&gt;&lt;P&gt;May i know what could be the reason for above issue and is there any fix for this?&lt;/P&gt;&lt;P&gt;Note : This application will read sensor data, gps data, CAN data and also file read/write operation to some text file. which is of less size.&lt;/P&gt;&lt;P&gt;When i checked in google, the bit corruption due to other reasons may not be handled properly. So what can be done for this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Feb 2020 10:02:23 GMT</pubDate>
    <dc:creator>velayutha_perum</dc:creator>
    <dc:date>2020-02-18T10:02:23Z</dc:date>
    <item>
      <title>UBIFS ReadOnly FS</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-ReadOnly-FS/m-p/982523#M145944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using iMx6ULL in our design with Toshiba NAND. When run my application more than a day , i m getting below errors,&lt;/P&gt;&lt;P&gt;UBIFS error (ubi0:0 pid 22611): ubifs_scan: corrupt empty space at LEB 1565:81920&lt;BR /&gt;UBIFS error (ubi0:0 pid 22611): ubifs_scanned_corruption: corruption at LEB 1565:81920&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): ubifs_scanned_corruption: first 8192 bytes from LEB 1565:81920&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): ubifs_scan: LEB 1565 scanning failed&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS error (ubi0:0 pid 22611): do_commit: commit failed, error -117&lt;BR /&gt;[2020-02-15 21:56:27] UBIFS warning (ubi0:0 pid 22611): ubifs_ro_mode: switched to read-only mode, error -117&lt;BR /&gt;[2020-02-15 21:56:27] CPU: 0 PID: 22611 Comm: sync Not tainted 4.1.15 #1&lt;BR /&gt;[2020-02-15 21:56:27] Hardware name: Freescale i.MX6 UL/ULL (Device Tree)&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80015a78&amp;gt;] from [&amp;lt;80012658&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80012658&amp;gt;] from [&amp;lt;8067b558&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;8067b558&amp;gt;] from [&amp;lt;80226e04&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;80226e04&amp;gt;] from [&amp;lt;802173b4&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;802173b4&amp;gt;] from [&amp;lt;800eb5c0&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;800eb5c0&amp;gt;] from [&amp;lt;801110dc&amp;gt;]&lt;BR /&gt;[2020-02-15 21:56:27] Function entered at [&amp;lt;801110dc&amp;gt;] from [&amp;lt;8000f400&amp;gt;]&lt;/P&gt;&lt;P&gt;I/O error : Read-only file system&lt;/P&gt;&lt;P&gt;May i know what could be the reason for above issue and is there any fix for this?&lt;/P&gt;&lt;P&gt;Note : This application will read sensor data, gps data, CAN data and also file read/write operation to some text file. which is of less size.&lt;/P&gt;&lt;P&gt;When i checked in google, the bit corruption due to other reasons may not be handled properly. So what can be done for this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 10:02:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-ReadOnly-FS/m-p/982523#M145944</guid>
      <dc:creator>velayutha_perum</dc:creator>
      <dc:date>2020-02-18T10:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: UBIFS ReadOnly FS</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-ReadOnly-FS/m-p/982524#M145945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Velayutha&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seems this is specific ubifs error and was reported many times:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://lists.infradead.org/pipermail/linux-mtd/2013-March/046149.html" title="http://lists.infradead.org/pipermail/linux-mtd/2013-March/046149.html"&gt;UBIFS corruption bug&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://linux-mtd.infradead.narkive.com/Bz5lUdif/ubifs-scan-corrupt-empty-space" title="https://linux-mtd.infradead.narkive.com/Bz5lUdif/ubifs-scan-corrupt-empty-space"&gt;ubifs_scan: corrupt empty space&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From log L4.1.15 kernel used, so may be recommended to try with latest kernels described on&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/design/i.mx-developer-resources/i.mx-software-and-development-tools:IMX-SW" title="https://www.nxp.com/design/i.mx-developer-resources/i.mx-software-and-development-tools:IMX-SW"&gt;i.MX Software and Development Tools | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Feb 2020 01:25:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-ReadOnly-FS/m-p/982524#M145945</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2020-02-21T01:25:01Z</dc:date>
    </item>
  </channel>
</rss>

