All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>,
	Ricard Wanderlof <ricard.wanderlof@axis.com>
Subject: Re: Grow UBI device?
Date: Thu, 10 Oct 2013 10:42:42 +0300	[thread overview]
Message-ID: <1381390962.7875.57.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA20350@DBDE04.ent.ti.com>

On Wed, 2013-10-09 at 11:28 +0000, Gupta, Pekon wrote:
> Yes, during mounting of UBIFS volumes, UBI checks for erase-header
> on first-page of every block. 
> - If it's able to find a valid erase-header, with correct image_seq field,
> then it attaches it to its pool.
> - Otherwise, if the valid erase-header was not found, then it assumes
>  then it ubi will try re-erasing it. And add it to its pool of free-blocks.

I think there is a separate list for blocks with garbage, and if UBI
finds too much of them, it attaches R/O. So if it would find too many
JFFS2 eraseblocks, it would not erase them. But erasing the JFFS2 blocks
from outside of UBI driver would help.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2013-10-10  7:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 19:28 Grow UBI device? Wolfgang Denk
2013-10-09  7:28 ` Matthieu CASTET
2013-10-09  8:46 ` Ricard Wanderlof
2013-10-09 11:28   ` Gupta, Pekon
2013-10-09 15:05     ` Wolfgang Denk
2013-10-09 15:45       ` Ricard Wanderlof
2013-10-09 18:47         ` Richard Weinberger
2013-10-09 20:01         ` Wolfgang Denk
2013-10-10  7:42     ` Artem Bityutskiy [this message]
2013-10-09 14:33   ` Wolfgang Denk
2013-10-10  8:17 ` Artem Bityutskiy
2013-10-10  8:34   ` Richard Weinberger
2013-10-15 17:40   ` Wolfgang Denk
2013-10-15 18:38     ` 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=1381390962.7875.57.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    --cc=ricard.wanderlof@axis.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.