From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Weinberger <richard@nod.at>
Date: Sat, 19 May 2018 10:37:55 +0200
Subject: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux
In-Reply-To: <CAEBv-SE0_kTEQkKbbKyE13PM=dMXYGbpWDv4M0+EEV7yzsAK8A@mail.gmail.com>
References: <CAEBv-SHJ=sDLKU3UcgK_ghTf3vzv7ti9yFSsj9cOKTyf74kwDw@mail.gmail.com>
 <6719649.hD5gWRHcFI@blindfold>
 <CAEBv-SE0_kTEQkKbbKyE13PM=dMXYGbpWDv4M0+EEV7yzsAK8A@mail.gmail.com>
Message-ID: <3321141.P3ba7yLJY1@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

Am Samstag, 19. Mai 2018, 01:56:33 CEST schrieb Otto Blom:
> UBIFS error (ubi0:0 pid 0): crypto_comp_decompress: cannot decompress
> 2801 bytes, compressor lzo, error -6

LZO_E_LOOKBEHIND_OVERRUN...

> UBIFS error (ubi0:0 pid 0): ubifs_decompress: cannot decompress 2801
> bytes, compressor lzo, error -6
> ubifs_decompress RC: -6 len: 4096  out_len: 3377
> UBIFS error (ubi0:0 pid 0): read_block: bad data node (block 3, inode 68)
>         magic          0x6101831
>         crc            0xf15144c6
>         node_type      1 (data node)
>         group_type     0 (no node group)
>         sqnum          3276
>         len            2849
>         key            (68, data, 3)
>         size           4096
>         compr_typ      1
>         data size      2801
>         data:
> UBIFS error (ubi0:0 pid 0): do_readpage: cannot read page 3 of inode
> 68, error -22
> Error reading file '/boot/Image'

So, LZO *does* return an error.
Did you edit the logs in your last mails? Or was some U-Boot silencing option
enabled?

Please double-check whether your setup is correct.
Does it work if you disable compression?

Your UBIFS image looks good.
I checked the data node by hand and was able to read that file on 4.9.100 and linus
as of today.

Thanks,
//richard