From: Adrian Hunter <adrian.hunter@intel.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Robert Homann <homann@bury.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: Resizing of an existing UBIFS
Date: Mon, 28 May 2012 12:09:40 +0300 [thread overview]
Message-ID: <4FC340D4.9020905@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1205250958290.4247@lnxricardw.se.axis.com>
On 25/05/12 11:00, Ricard Wanderlof wrote:
>
> On Fri, 25 May 2012, Robert Homann wrote:
>
>> It is definitely a lot simpler to just set this parameter to some big
>> value and generate new images from scratch since the overhead in space
>> consumption is not an issue in this case. But let's say, in my case the
>> purpose of using such a resizing tool is not space optimization, but
>> fixing a former decision...
>
> I think this is a most important point. Whatever sizing strategy and volume
> sizes that are decided upon, one can be sure that a couple of years down the
> line differing circumstances will require a re-think of that strategy, no
> matter how well founded the decision was to start with.
Unless you set max_leb_cnt to match the media size.
The point is resizing when max_leb_cnt is not changed is much simpler.
next prev parent reply other threads:[~2012-05-28 9:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 6:41 Resizing of an existing UBIFS Robert Homann
2012-05-22 6:53 ` Artem Bityutskiy
2012-05-22 7:21 ` Robert Homann
2012-05-22 8:10 ` Artem Bityutskiy
2012-05-22 9:25 ` Robert Homann
2012-05-22 9:40 ` Ricard Wanderlof
2012-05-22 10:19 ` Artem Bityutskiy
2012-05-22 11:11 ` Robert Homann
2012-05-22 11:24 ` Artem Bityutskiy
2012-05-25 7:00 ` Adrian Hunter
2012-05-25 7:49 ` Robert Homann
2012-05-25 8:00 ` Ricard Wanderlof
2012-05-28 9:09 ` Adrian Hunter [this message]
2012-06-01 10:10 ` Ricard Wanderlof
2012-06-01 11:48 ` Adrian Hunter
2012-06-01 19:47 ` Ricard Wanderlof
2012-06-04 7:58 ` Adrian Hunter
2012-06-04 9:35 ` Ricard Wanderlof
2012-06-04 9:47 ` Artem Bityutskiy
2012-05-25 10:12 ` Norbert van Bolhuis
2012-05-26 14:00 ` Artem Bityutskiy
2012-05-27 20:24 ` Norbert van Bolhuis
2012-05-28 5:46 ` 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=4FC340D4.9020905@intel.com \
--to=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=homann@bury.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;
as well as URLs for NNTP newsgroup(s).