From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Artem Bityutskiy <dedekind1@gmail.com>
Cc: Heinz.Egger@linutronix.de, tglx@linutronix.de,
linux-mtd@lists.infradead.org, tim.bird@am.sony.com,
adrian.hunter@intel.com
Subject: Re: ubi: fastmap: v7: ubi_update_fastmap failure
Date: Tue, 5 Jun 2012 23:20:49 +0300 [thread overview]
Message-ID: <20120605232049.1e4f5184@halley> (raw)
In-Reply-To: <4FCE0E81.9000705@nod.at>
Hi,
On Tue, 05 Jun 2012 15:49:53 +0200 Richard Weinberger <richard@nod.at> wrote:
> Am 05.06.2012 15:41, schrieb Shmulik Ladkani:
> > Hi Richard,
> >
> > I got the below UBI error when working with fastmap v7 (linux-ubi.git,
> > branch fastmap, HEAD at bd8313d).
> >
> > Had no time to investigate (could be fixed by your v7+ patches); please
> > take a look if you can.
> >
> > Setup:
> > - Beagle with SLC NAND.
> > - ubi.mtd=4 root=ubi0:beagleboard-rootfs rootfstype=ubifs
> > - A single volume on the ubi0 device (the ubifs rootfs).
> >
> > The board booted several times succesfully with fastmap-v7.
> > Then I got the error below, when ubifs was mounted (note UBI attach was
> > successful).
> >
> > Switched to non-fastmap kernel, board booted successfully (with ubifs
> > mounted succesfully).
> >
> > Regards,
> > Shmulik
> >
> > [ 3.222808] UBIFS: recovery needed
> > [ 3.281646] UBI error: __ubi_wl_get_peb: no free eraseblocks
> > [ 3.287750] UBI error: ubi_wl_get_fm_peb: no free eraseblocks
> > [ 3.294952] UBI error: ubi_update_fastmap: Erase counter overflow!
>
> Please use v7+.
> It looks like you need:
> [PATCH 01/23] UBI: Fastmap: Fix EC overflow calculation
Thanks, will retest.
BTW, a UBIFS question.
Any idea why UBIFS failed to mount eventually?
As you can see, both UBI and UBIFS switched themselves to RO mode. Okay.
However eventually, the mount failed.
Regards,
Shmulik
next prev parent reply other threads:[~2012-06-05 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 13:41 ubi: fastmap: v7: ubi_update_fastmap failure Shmulik Ladkani
2012-06-05 13:49 ` Richard Weinberger
2012-06-05 14:01 ` Artem Bityutskiy
2012-06-05 20:20 ` Shmulik Ladkani [this message]
2012-06-05 20:31 ` Richard Weinberger
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=20120605232049.1e4f5184@halley \
--to=shmulik.ladkani@gmail.com \
--cc=Heinz.Egger@linutronix.de \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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.