linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andrew Murray <amurray@mpcdata.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: validate_sb: bad superblock, error 8 (Minimum UBI volume size for UBIFS image)
Date: Sun, 16 Jan 2011 00:22:49 +0200	[thread overview]
Message-ID: <1295130169.2516.4.camel@koala> (raw)
In-Reply-To: <AANLkTinyjaXqfWBSXzG2jg8wWiVbXA6ZhZ=RUgtue=qO@mail.gmail.com>

On Sat, 2011-01-15 at 22:09 +0000, Andrew Murray wrote:
> On 15 January 2011 10:48, Andrew Murray <amurray@mpcdata.com> wrote:
> > On 11 January 2011 09:47, Andrew Murray <amurray@mpcdata.com> wrote:
> >>
> >> Is there a way to determine the minimum UBI volume size which will
> >> support a given UBIFS filesystem image?
> >>
> >
> > My conclusion is this (with my version of kernel and mkfs.ubifs tool):
> >
> > (Min No. UBI Volume LEBS) = (jrn_lebs) + 3 + (log lebs) + (lpt_lebs) +
> > (orph_lebs)
> >
> > And these values can all be determined (or specified) by the
> > mkfs.ubifs tool by using the verbose -v flag.
> >
> > This seems to hold true - Does this seem reasonable?
> 
> After reading the ODP presentation, white paper and reading the source
> - I do not understand the purpose of the second condition in the
> following test case in validate_sb:
> 
>         if (c->max_bud_bytes < (long long)c->leb_size * UBIFS_MIN_BUD_LEBS ||
>             c->max_bud_bytes > (long long)c->leb_size * c->main_lebs
> 
> It seems to be asserting that there is enough space on the volume to
> cater for the maximum size of the journal. However in the case where
> the UBI volume is similar in size to the UBIFS image data -
> 'main_lebs' will mostly be absent of free space lebs. Therefore there
> may not be enough room for max_bud_bytes amounts of journal. And in
> any case the journal code seems to cater well for there not being
> enough free lebs. (Presumably it copes when the volume is nearly
> full).
> 
> Therefore is this condition superfluous?

Hi, I'm not able to give you any reasonable answer right now (vacation,
and already have long backlog of e-mails to answer), sorry for this. But
the space calculations may have issues - we did not work on that well
enough, and did not test them with different journal sizes, etc. Just
did not spend much time on those things - wrote the code which
calculates some default sizes and used that all the time. AFSIK,
mkfs.ubifs is mostly copy-paste of the kernel code, including the
default geometry calculations.

Please, feel free to send patches.

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2011-01-15 22:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  9:47 validate_sb: bad superblock, error 8 (Minimum UBI volume size for UBIFS image) Andrew Murray
2011-01-15 10:48 ` Andrew Murray
2011-01-15 22:09   ` Andrew Murray
2011-01-15 22:22     ` Artem Bityutskiy [this message]
2011-01-18  9:41     ` Artem Bityutskiy
2011-01-18  9:18   ` Artem Bityutskiy
2011-01-18  9:16 ` Artem Bityutskiy
2011-01-18  9:30   ` Artem Bityutskiy
2011-01-18  9:50     ` 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=1295130169.2516.4.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=amurray@mpcdata.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;
as well as URLs for NNTP newsgroup(s).