public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Doug Kehn <rdkehn@yahoo.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: UBI: Single versus Multiple Images
Date: Tue, 5 Jun 2012 06:21:40 -0700 (PDT)	[thread overview]
Message-ID: <1338902500.33577.YahooMailNeo@web39302.mail.mud.yahoo.com> (raw)

Hi Everyone,

I have the following NAND flash MTD layout (presently JFFS2):

* Boot-loader
* Kernel
* Root file-system (rootfs)

* Data

I'm going to switch from JFFS2 to UBI/UBIFS.  I'm wondering if it is better to create a single UBI image containing both rootfs and data volumes or to create separate UBI images (each with a single volume) or is the answer it depends?

The data volume will be used for logging data.  The volume won't completely fill as old data will be purged to make room for new data.  For the single image multiple volume case, if I understand the 
documentation correctly, UBI will use all PEB from both volumes for mapping per-volume LEB, 
correct?  If my understanding is correct, then it's possible, after enough time, maximum PEB erase count will be reached and both rootfs and data volumes will be read-only?  If the goal is to keep the rootfs volume writable, even if the data volume become read-only, then would it be better to create multiple UBI images?  Or is my understanding all wrong?

Thanks,
...doug

             reply	other threads:[~2012-06-05 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 13:21 Doug Kehn [this message]
2012-06-06  9:14 ` UBI: Single versus Multiple Images Artem Bityutskiy
2012-06-06 11:53   ` Doug Kehn

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=1338902500.33577.YahooMailNeo@web39302.mail.mud.yahoo.com \
    --to=rdkehn@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox