From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brent Taylor <motobud@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS Recovery Issue: 'grab_empty_leb: could not find an empty LEB'
Date: Fri, 31 Aug 2012 14:44:29 +0300 [thread overview]
Message-ID: <1346413469.9709.44.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAP+RiCC1afVbKAZESMcZGd1G3+7aKuLTQGggOEFGZxQM6o+QQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Mon, 2012-07-16 at 13:22 -0500, Brent Taylor wrote:
> I'm developing on custom hardware using an at91sam9g45 processor with
> 64 MB of RAM and 64 MB of NOR flash running Linux 3.0.13.
>
> I'm doing some power-cycle testing and after several hours, UBIFS
> failed to mount the root partition and printed the message
> "grab_empty_leb: could not find an empty LEB". The system boots and
> starts a script that will power cycle the board anytime between 10 and
> 20 seconds after the script has started. Just before a power cycle
> occurs, syslog and our main process are the only processes that could
> be writing to disk.
>
I was trying to do power cut emulation testing with mtdram, and I see
there are some issues which do not seem to exist on NAND. But they are
different to yours. I remember I saw these -ENOSPC issues in the past,
but they were very difficult to reproduce.
I will try to investigate why power-cut emulation testing fails on
mtdram, but I have limited amount of time and I do not know when I'll be
able to do this.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-31 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 18:22 UBIFS Recovery Issue: 'grab_empty_leb: could not find an empty LEB' Brent Taylor
2012-08-13 13:41 ` Brent Taylor
2012-08-17 12:57 ` Artem Bityutskiy
2012-08-24 15:59 ` Brent Taylor
2012-08-24 16:13 ` Artem Bityutskiy
2012-08-17 12:50 ` Artem Bityutskiy
2012-08-31 11:44 ` Artem Bityutskiy [this message]
[not found] ` <CAP+RiCBRopbShAGf_fWCvK2R=uPPR1j4Pz12JfJxdEMUjwofNw@mail.gmail.com>
2012-09-17 13:34 ` Brent Taylor
2012-09-23 15:48 ` Brent Taylor
2012-09-23 16:03 ` Artem Bityutskiy
2012-10-09 13:30 ` Artem Bityutskiy
[not found] ` <CAP+RiCBCe-KUu+dd5NTizMoJU4gd+r5o=VmBa4CauP704uSmbQ@mail.gmail.com>
2012-10-09 17:25 ` Artem Bityutskiy
2012-10-04 15:05 ` Artem Bityutskiy
2012-10-09 12:00 ` 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=1346413469.9709.44.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=motobud@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.