From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Weinberger <richard@nod.at>
Date: Tue, 22 May 2018 08:24:37 +0200
Subject: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux
In-Reply-To: <CAEBv-SHPiCynNcEkZWGk3yR+BqivT-56ErtAk9zzqiXEb6iYaw@mail.gmail.com>
References: <CAEBv-SHJ=sDLKU3UcgK_ghTf3vzv7ti9yFSsj9cOKTyf74kwDw@mail.gmail.com>
 <3321141.P3ba7yLJY1@blindfold>
 <CAEBv-SHPiCynNcEkZWGk3yR+BqivT-56ErtAk9zzqiXEb6iYaw@mail.gmail.com>
Message-ID: <8506860.QLH14q6iHR@blindfold>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Otto,

Am Dienstag, 22. Mai 2018, 03:30:04 CEST schrieb Otto Blom:
> Hi Richard !
> 
> To summarize the observations from the last few days.
> 
> * Linux 4.9 & U-boot 2018 behave the same when attempting to read from
> a ubifs file system
> * Whenever Linux 4.14 writes to a ubifs there is some form of
> incompatibility introduced
> causing assorted errors when the file system is read in Linux 4.9 or
> U-boot. However
> the files can still be read in Linux 4.14.
> 
> This lead me to suspect a problem with the OOB data. So I copied over
> a 16MB textfile to
> a freshly minted no-compression ubifs partition (running 4.14) and ran
> a nanddump both from
> Linux 4.9 and 4.14 and the contents are different - Bit errors are
> present in the 4.9-dump..

This smells like a problem on MTD/NAND-Level.
Decompression might fail because bits changes but didn't get fixed by your driver.

Thanks,
//richard