All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Hevern <matt.hevern@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS becomes read-only when written, then fails to mount
Date: Thu, 3 Jul 2014 11:20:42 +1000	[thread overview]
Message-ID: <20140703012041.GB19950@gmail.com> (raw)
In-Reply-To: <1404222952.6841.92.camel@sauron.fi.intel.com>

On Tue, Jul 01, 2014 at 04:55:52PM +0300, Artem Bityutskiy wrote:
> On Wed, 2014-06-18 at 14:44 +1000, Matt Hevern wrote:
> > Hi All,
> > 
> > 
> > I am running UBIFS on freescale i.MX28, kernel 2.6.35.3, based on
> > freescale's IMX tree:
> > http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/?h=imx_2.6.35_maintain
> > The flash is NAND, Micron 256MiB (MT29F2G08)
> 
> In your dumps I see that there are errors related to UBIFS not being
> able to find an LEB for the garbage collector. And I remember we fixed
> bugs in this area.
> 
> For example, "6fb4374 UBIFS: fix GC LEB recovery", and there were more.
> Search for 'ubifs_rcvry_gc_commit' in 'git log -p fs/ubifs/recovery.c'.


Thanks for your response. I can see that I don't currently have this commit.
I'll attempt to pull in this and any others that look relevant.

Thanks,


Matt

  reply	other threads:[~2014-07-03  1:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  4:44 UBIFS becomes read-only when written, then fails to mount Matt Hevern
2014-06-18  9:48 ` Tanya Brokhman
2014-06-18 11:02   ` Matt Hevern
2014-06-18 11:14     ` Tanya Brokhman
2014-06-18 11:45       ` Matt Hevern
2014-06-18 12:32         ` Tanya Brokhman
2014-06-18 13:12           ` Matt Hevern
2014-07-01 13:55 ` Artem Bityutskiy
2014-07-03  1:20   ` Matt Hevern [this message]
2014-07-03  5:16   ` Matt Hevern

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=20140703012041.GB19950@gmail.com \
    --to=matt.hevern@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.