linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Leo Barnes <barnes.leo@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CRC error when mounting UBIFS
Date: Thu, 03 Jun 2010 17:25:18 +0300	[thread overview]
Message-ID: <1275575118.9729.2.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilGg81TGnkS2VwF6xdFCvsB_AF_8rLYVqTr-81g@mail.gmail.com>

On Thu, 2010-06-03 at 16:02 +0200, Leo Barnes wrote:
> Hello!
> 
> I am trying to create and mount an UBIFS partition and get the
> following error when trying to mount it:
> <7>[  397.117065] UBIFS DBG (pid 438): ubifs_start_scan: scan LEB 490:0
> <7>[  397.117218] UBIFS DBG (pid 438): ubifs_scan: look at LEB 490:0
> (126976 bytes left)
> <7>[  397.117401] UBIFS DBG (pid 438): ubifs_scan_a_node: hit empty space
> <7>[  397.117614] UBIFS DBG (pid 438): ubifs_end_scan: stop scanning
> LEB 490 at offset 0
> <3>[  397.119598] UBIFS error (pid 438): check_lpt_crc: invalid crc in
> LPT node: crc 0 calc 90d1

Most of the time errors like this are because of problems in the driver
level, e.g., when the driver does not handle small or unaligned length
reads. Did you validate your MTD driver with MTD tests?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-06-03 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 14:02 CRC error when mounting UBIFS Leo Barnes
2010-06-03 14:25 ` Artem Bityutskiy [this message]
2010-06-03 15:14   ` Leo Barnes
2010-06-03 15:32     ` Artem Bityutskiy
2010-06-04 16:18       ` Leo Barnes
2010-06-04 17:03         ` Artem Bityutskiy
2010-06-04 17:35           ` Leo Barnes
2010-06-04 18:01             ` Artem Bityutskiy
2010-06-18 18:02         ` Artem Bityutskiy
2010-06-03 15:41     ` 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=1275575118.9729.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;
as well as URLs for NNTP newsgroup(s).