From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: barebox@lists.infradead.org
Subject: Broken ubifs-zstd
Date: Tue, 27 Sep 2022 19:21:33 +0200 [thread overview]
Message-ID: <lyr0zw68de.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
Hello,
trying to mount a zstd compressed ubifs fails on an iMX6ULL with
| ERROR: UBIFS error (ubi0:0): 9fe6691d: cannot decompress 2612 bytes, compressor zstd, error -22
| ERROR: UBIFS error (ubi0:0): 9fe6692d: cannot decompress 2612 bytes, compressor zstd, error -22
| ERROR: UBIFS error (ubi0:0): 9fe66a65: bad data node (block 0, inode 815)
| ERROR: magic 0x6101831
(2022.09 and master).
After reverting
| commit b4a9782d4f56333e897dccc35c2c27e2605f6b93
| Author: Ahmad Fatoum <a.fatoum@pengutronix.de>
| Date: Wed Jul 13 12:09:18 2022 +0200
|
| lib: zstd: sync with Linux
it works again (both in Linux 5.15 and barebox).
ubifs was created by recent OpenEmbedded kirkstone with
| MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 2048 --compr=zstd"
Warnings are triggered (after fixing assert()) at
| WARNING: at lib/zstd/decompress/../common/bitstream.h:390/BIT_reloadDStreamFast()!
Is anybody else experiencing these problems?
Enrico
next reply other threads:[~2022-09-27 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 17:21 Enrico Scholz [this message]
2022-09-27 17:45 ` Ahmad Fatoum
2022-09-28 10:18 ` Info Skymem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lyr0zw68de.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox