public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBI/ubifs problem
Date: Fri, 09 Mar 2012 15:39:26 +0200	[thread overview]
Message-ID: <1331300366.29445.31.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1203080606110.24516@lnxricardw.se.axis.com>

On Thu, 2012-03-08 at 06:09 +0100, Ricard Wanderlof wrote:
> On Wed, 7 Mar 2012, Artem Bityutskiy wrote:
> 
> > On Wed, 2012-03-07 at 17:26 +0100, Ricard Wanderlof wrote:
> >> Is it possible to get mkfs.ubifs to create an image without specifying the
> >> max-leb-count ? I.e. just to create an image that is as big as it has to
> >> be.
> >
> > Has to be? :-) Not sure how to find this out. Basically the idea was
> > that you know how big is has to be and translate that to
> > --max-leb-count.
> 
> I think what I'm thinking about is that in the specialized case of ubifs 
> used for a read-only file system, such as a root file system (without 
> /etc, /var, and so on), it would be possible for mkfs.ubifs to create a 
> file system, and use as many LEBs as it needs for the actual data. On a 
> read-only file system there doesn't even have to be a journal, although I 
> don't know if that is possible.

Well, I'd accept a patch which added a --optimize-for-ro option which
would prepare a file-system with the smallest journal size.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2012-03-09 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 15:17 UBI/ubifs problem Ricard Wanderlof
2012-02-17 10:13 ` Ricard Wanderlof
2012-03-07 14:40   ` Artem Bityutskiy
2012-03-07 16:26     ` Ricard Wanderlof
2012-03-07 16:37       ` Artem Bityutskiy
2012-03-08  5:09         ` Ricard Wanderlof
2012-03-09 13:39           ` Artem Bityutskiy [this message]
2012-03-09 13:45             ` Ricard Wanderlof
2012-03-09 13:51               ` Artem Bityutskiy
2012-03-07 16:51       ` Paul Parsons

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=1331300366.29445.31.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox