From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubifs image file confusion!
Date: Wed, 14 May 2008 16:23:44 +0300 [thread overview]
Message-ID: <1210771424.5708.54.camel@sauron> (raw)
In-Reply-To: <bae050c10805080256v576323fy45d607c39593cdd@mail.gmail.com>
On Thu, 2008-05-08 at 17:56 +0800, Nancy wrote:
> #ubiupdate /dev/ubi0_0 ubifs.dp (generated by ubidumpvol)
>
> # mount -t ubifs ubi0:ubifs /mnt/1
> UBIFS: mounted UBI device 0, volume 0
> UBIFS: minimal I/O unit size: 2048 bytes
> UBIFS: logical eraseblock size: 258048 bytes (252 KiB)
> UBIFS: file system size: 102445056 bytes (100044 KiB, 97 MiB, 397 LEBs)
> UBIFS: journal size: 9420800 bytes (9200 KiB, 8 MiB, 37 LEBs)
> UBIFS: data journal heads: 1
> UBIFS: default compressor: LZO
> UBIFS error (pid 598): ubifs_check_node: bad magic 0xffffffff, expected 0x610181
> UBIFS error (pid 598): ubifs_check_node: bad node at LEB 143:189920
This looks like you have not flashed UBIFS image properly or it was not
generated properly. UBIFS index refers a node, but the node is not there
and there are 0xFFs instead.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-05-14 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 9:17 ubifs image file confusion! Nancy
2008-05-08 9:56 ` Nancy
2008-05-14 13:23 ` Artem Bityutskiy [this message]
2008-05-08 10:48 ` Artem Bityutskiy
2008-05-09 7:05 ` Nancy
2008-05-10 4:20 ` Nancy
2008-05-10 7:31 ` Nancy
2008-05-13 9:48 ` Artem Bityutskiy
2008-05-13 12:52 ` Nancy
2008-05-14 13:45 ` Artem Bityutskiy
2008-05-15 4:06 ` Nancy
2008-05-13 9:44 ` Artem Bityutskiy
2008-05-13 12:41 ` Nancy
2008-05-14 13:20 ` Artem Bityutskiy
2008-05-15 3:18 ` Nancy
2008-07-08 10:45 ` 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=1210771424.5708.54.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.