All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS failed to recover master node
Date: Tue, 25 May 2010 08:06:22 +0300	[thread overview]
Message-ID: <1274763982.2106.2.camel@localhost> (raw)
In-Reply-To: <AANLkTimPxrQzSS_n6CofW8ePwCKuE7sbENJZXUl1Yszl@mail.gmail.com>

On Mon, 2010-05-24 at 11:22 -0400, twebb wrote:
> I've had several cases where our MLC NAND flash appears corrupted in
> such a way that one of three UBIFS volumes can not be mounted due to
> "failed to recover master node".  I haven't been able to reproduce the
> problem, but we've had at least 5 incidents where this has occurred.
> (A partial capture from one of the failures is below.)
> 
> I'm starting to investigate this problem and don't know if this is a
> UBIFS/UBI problem or a NAND driver problem.  I'm starting the process
> of back-porting the latest UBIFS code to our 2.6.29 kernel - hoping
> that new UBIFS code will solve the problem.  However, this may also be
> a driver problem and I wonder if I also need to update that driver
> (pxa3xx_nand).  Any suggestions for debugging this problem?
> 
> Thanks,
> twebb
> 
> 
> capture:
> [root@ESIedge mtd-utils]# mount -t ubifs ubi0_0 /mnt/
> [  239.605869] UBI error: ubi_io_read: error -74 while reading 516096
> bytes from PEB 4:8192, read 516096 bytes
> [  239.616317] UBIFS error (pid 676): ubifs_scan: corrupt empty space
> at LEB 2:268135
> [  239.623996] UBIFS error (pid 676): ubifs_scanned_corruption:
> corruption at LEB 2:268135
> [  239.642101] UBIFS error (pid 676): ubifs_scan: LEB 2 scanning failed
> [  239.976396] UBI error: ubi_io_read: error -74 while reading 516096
> bytes from PEB 4:8192, read 516096 bytes
> [  239.986742] UBIFS error (pid 676): ubifs_recover_master_node:
> failed to recover master node
> mount: mounting ubi0_0 on /mnt/ failed: Invalid argument

And BTW, it is a good idea not to erase/re-flash this device if you want
to fix this problem.

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

  parent reply	other threads:[~2010-05-25  5:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 15:22 UBIFS failed to recover master node twebb
2010-05-25  5:05 ` Artem Bityutskiy
2010-05-26 16:06   ` twebb
2010-05-26 16:32     ` Artem Bityutskiy
2010-06-08 13:44   ` twebb
2010-06-08 14:17     ` Artem Bityutskiy
2010-06-08 15:00       ` twebb
2010-06-08 15:23         ` twebb
2010-06-08 15:33       ` twebb
2010-06-10 13:08       ` twebb
2010-06-10 13:14         ` Artem Bityutskiy
2010-05-25  5:06 ` Artem Bityutskiy [this message]
2010-06-28  8:21   ` re
2010-07-13  8:48     ` 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=1274763982.2106.2.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=taliaferro62@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.