All of lore.kernel.org
 help / color / mirror / Atom feed
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, 24 Aug 2012 19:13:00 +0300	[thread overview]
Message-ID: <1345824780.2848.342.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAP+RiCASzaH-TFHSYK0ioyXackRcMrZD4eoev2qVUVLhGft7Bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

On Fri, 2012-08-24 at 10:59 -0500, Brent Taylor wrote:
> On Fri, Aug 17, 2012 at 7:57 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> >
> > On Mon, 2012-08-13 at 13:41 +0000, Brent Taylor wrote:
> > > I've been running with the patched kernel for about a month now and I've seen
> > > this issue once since then.  Does anyone have any other ideas on how I can
> > > better track this down.  I've taken precautions to test if the external data
> > > partitions mounted properly, if not, then they are reformatted and initialized.
> > >  I will have a problem if the issue occurs in the root filesystem.
> >
> > What kind of test do you run?
> >
> > --
> > Best Regards,
> > Artem Bityutskiy
> 
> 
> Artem,
> Thanks for taking the time to look at this.
> 
> I'm not sure if I can share the image just yet.  What all would you
> need?  vmlinuz, uImage, the config file?.

No. dd if=/dev/mtd4 of=image

and share the image. I could try to put it to mtdram and mount the
volume, and take a closer look at the error.

But I think I saw these errors before when testing, they were so rare,
and I did not have time to dig.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-08-24 16:08 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 [this message]
2012-08-17 12:50 ` Artem Bityutskiy
2012-08-31 11:44 ` Artem Bityutskiy
     [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=1345824780.2848.342.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.