public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: sid@ics.uci.edu
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs mount failure upon power cycle
Date: Wed, 06 Jan 2010 16:32:44 +0200	[thread overview]
Message-ID: <1262788364.3177.13.camel@localhost> (raw)
In-Reply-To: <ba9f10a6e8ef14a2d032fba7f1686df9.squirrel@webmail.ics.uci.edu>

Hello,

On Fri, 2009-12-11 at 10:28 -0800, sid@ics.uci.edu wrote:
> I'm trying to use UBIFS (linux 2.6.31) on a MIPS based platform, 128 MB
> SLC (2k page) NAND flash as rootfs. After erasing the flash and mounting
> ubifs as rootfs, I do a large amount of file copies from NFS. However, if
> there is an abrupt power cycle, upon reboot the rootfs mount fails with
> the following error messages:
> 
> UBIFS: recovery needed
> UBIFS error (pid 1): ubifs_scan: corrupt empty space at LEB 6:43008
> UBIFS error (pid 1): ubifs_scanned_corruption: corruption at LEB 6:43008
> UBIFS error (pid 1): ubifs_scan: LEB 6 scanning failed
> UBIFS error (pid 1): ubifs_recover_leb: corrupt empty space LEB 6:24576,
> corruption starts at 18432
> UBIFS error (pid 1): ubifs_scanned_corruption: corruption at LEB 6:18432
> UBIFS error (pid 1): ubifs_recover_leb: LEB 6 scanning failed
> VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1)
> 
> I searched the list for similar messages. There was a similar thread
> (http://lists.infradead.org/pipermail/linux-mtd/2009-April/025229.html)
> for NOR flash. However, the fixes to recovery.c from that thread are
> already in the current sources.
> 
> Any suggestions/pointers on how to debug/fix would be greatly appreciated.

No idea why this could happen. Did you try do narrow down the problem to
a simpler use-case?

That thread was about NOR, that should not happen on NAND. This looks
like you have issues on NAND flash driver or HW level, not in UBI/UBIFS.

Please, start from running MTD tests and validate you NAND:
http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests

And next time please try to follow these bug-report suggestions:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport

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

      reply	other threads:[~2010-01-06 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 18:28 ubifs mount failure upon power cycle sid
2010-01-06 14:32 ` Artem Bityutskiy [this message]

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=1262788364.3177.13.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sid@ics.uci.edu \
    /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