From: Artem Bityutskiy <dedekind1@gmail.com>
To: Leo Barnes <barnes.leo@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.ubifs gives corrupt images/crc errors
Date: Tue, 27 Jul 2010 16:39:55 +0300 [thread overview]
Message-ID: <1280237995.3021.2.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTin+3QMqZvMNgvKTH0F_ZngY9ooBR7sSKW5cdJUq@mail.gmail.com>
On Tue, 2010-07-27 at 09:03 +0200, Leo Barnes wrote:
> Hello!
>
> The recent versions of mkfs.ubifs in the mtd-utils gives corrupt
> images for me. I get the following error messages when trying to mount
> the ubi-volume:
>
> <3>[ 711.246826] UBIFS error (pid 413): ubifs_check_node: bad CRC:
> calculated 0x1f8f89ca, read 0xbb39064c
> <3>[ 711.247558] UBIFS error (pid 413): ubifs_check_node: bad node at LEB 0:0
> <3>[ 711.247924] UBIFS error (pid 413): ubifs_read_node: expected node type 6
>
> I have identified it as being broken since (approximately) after
> commit 004760f969175da7392dd02bb4fa14164ff46c1e (Wed Jun 16 09:47:27
> 2010 +0300). Two or three of the commits after this one refuse to
> build with various make errors, and the next one that builds gives
> corrupt images. It seems to have something to do with the CRC
> calculation.
Could you please find the commit which moves CRC support out of
mtd-utils/mkfs.ubifs and investigate what changed please? I think you
will find the reason quite quickly.
I'm on holiday, cannot look at this now.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-07-27 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 7:03 mkfs.ubifs gives corrupt images/crc errors Leo Barnes
2010-07-27 13:39 ` Artem Bityutskiy [this message]
2010-07-28 8:57 ` Leo Barnes
2010-07-28 12:15 ` Joakim Tjernlund
2010-08-22 8:22 ` Artem Bityutskiy
2010-09-02 17:28 ` Leo Barnes
2010-09-02 17:40 ` Artem Bityutskiy
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=1280237995.3021.2.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=barnes.leo@gmail.com \
--cc=linux-mtd@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