public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: ubifs error : read_znode: bad indexing node
Date: Mon, 11 Jun 2012 15:59:50 +0200	[thread overview]
Message-ID: <4FD5F9D6.9020800@parrot.com> (raw)

Hi,

we have products where rw ubifs partition are corrupted.
They all failed with the "read_znode: bad indexing node at LEB 558:22056, error
6" or "read_znode: bad indexing node at LEB 446:62888, error 2".

The last ubifs stable commit we have is
http://git.infradead.org/users/dedekind/ubifs-v2.6.32.git/commit/7eb3b6c0999bd2cbc37adb2bd0fb8127f98240ea
.


Do you know if the bug is known ?
Google doesn't provide any info on this and looking at ubifs new commits don't
provide explicit bug fix.

Are there any document that explain how znode works ?


Matthieu

             reply	other threads:[~2012-06-11 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 13:59 Matthieu CASTET [this message]
2012-06-18 20:45 ` ubifs error : read_znode: bad indexing node Artem Bityutskiy
2012-06-20  9:51   ` Matthieu CASTET
2012-06-20 11:03     ` 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=4FD5F9D6.9020800@parrot.com \
    --to=matthieu.castet@parrot.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