From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: shrinking ubifs?
Date: Mon, 01 Feb 2010 06:30:37 +0200 [thread overview]
Message-ID: <1264998637.2517.4.camel@localhost.localdomain> (raw)
In-Reply-To: <152584231001312001s51aa46c3y8c992d7f14c69f1a@mail.gmail.com>
On Sun, 2010-01-31 at 23:01 -0500, Jon Ringle wrote:
> On Wed, Jan 27, 2010 at 11:35 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Wed, 2010-01-27 at 11:34 -0500, Jon Ringle wrote:
> >> On Wed, Jan 27, 2010 at 11:25 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> >> > On Fri, 2010-01-22 at 14:21 -0500, Jon Ringle wrote:
> >> >> How about the opposite. If the static volumes became smaller freeing
> >> >> up some LEBs. Can the UBIFS be expanded to make use of the freed LEBs?
> >> >
> >> > That works automatically. UBIFS expands automatically, but up to the
> >> > size which you specified with the '-c' mkfs.ubifs option.
> >>
> >> Can the same thing be done using ubimkvol?
> >> ubimkvol -m -N ubifs /dev/ubi0
> >
> > Sorry, I don't understand the question...
>
> I create my ubi volumes from an initramfs environment that is compiled
> against klibc. So far, I haven't been able to build mkfs.ubifs against
> klibc, so I create my ubifs volume by using ubimkvol and then mounting
> it as ubifs.
I see. Well, that is about UBIFS, about the default formatting code,
when UBIFS formats empty volume. That code should be hacked and the
maximum FS size should be increased to the value you need.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-02-01 4:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 22:15 shrinking ubifs? Jon Ringle
2010-01-17 10:40 ` Artem Bityutskiy
2010-01-22 19:21 ` Jon Ringle
2010-01-27 16:25 ` Artem Bityutskiy
2010-01-27 16:34 ` Jon Ringle
2010-01-27 16:35 ` Artem Bityutskiy
2010-02-01 4:01 ` Jon Ringle
2010-02-01 4:30 ` 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=1264998637.2517.4.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=jon@ringle.org \
--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