All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Resizing of an existing UBIFS
Date: Mon, 28 May 2012 08:46:55 +0300	[thread overview]
Message-ID: <1338184015.2480.3.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FC28D71.1040107@aimvalley.nl>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

On Sun, 2012-05-27 at 22:24 +0200, Norbert van Bolhuis wrote:
> On 05/26/12 16:00, Artem Bityutskiy wrote:
> > On Fri, 2012-05-25 at 12:12 +0200, Norbert van Bolhuis wrote:
> >> This is not a problem for a UBIFS being created dynamically, so with
> >> ubiformat + ubiattach + ubimkvol ? In this case the size of the lprops
> >> area is determined by the total amount of LEBs of the MTD partition ?
> >
> > No, it is set according to the --max-leb-cnt parameter. Then UBIFS will
> > be able to grow up to "--max-leb-cnt" easily.
> >
> >> A UBIFS volume can then be resized with ubirsvol as long as it does not
> >> conflict with other volumes and does not exceed the total amount of
> >> LEBs of the MTD partition ?
> >
> > Yes, and if you resize withing '--max-leb-cnt', the UBIFS will
> > automatically resize itself.
> >
> > http://linux-mtd.infradead.org/faq/ubifs.html#L_max_leb_cnt
> >
> 
> I was asking because there is no --max-leb-cnt parameter wen creating a UBIFS
> dynamically, or is there ?

Ah, you mean when mounting an empty volume? No there is not, UBIFS just
picks some value.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-05-28  5:43 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
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 [this message]

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=1338184015.2480.3.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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.