public inbox for linux-mtd@lists.infradead.org
 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: Tue, 18 Jan 2011 11:50:42 +0200	[thread overview]
Message-ID: <1295344242.2470.117.camel@koala> (raw)
In-Reply-To: <1295343055.2470.105.camel@koala>

On Tue, 2011-01-18 at 11:30 +0200, Artem Bityutskiy wrote:
> On Tue, 2011-01-18 at 11:16 +0200, Artem Bityutskiy wrote:
> > Anyway, the only way for the user to affect the minimum FS size is the
> > --jrn-size option of mkfs.ubifs. How to calculate what will be the
> > minimum? Not sure, probably UBIFS_MIN_JNL_LEBS = 5 LEBs or something
> > close to this.
> 
> Ah, this is wrong, you can set the log size with --log-lebs as well.
> 
> So UBIFS journal = log + buds.
> 
> --log-lebs set the log size
> --jrn-size sets the buds size.

And note, strictly speaking --jrn-size is about buds size. This is
confusing naming. But I think we wanted to hide complexities from the
user and make him think that the journal is some area of fixed size, and
--jrn-size defines it. But probably that was a bad idea, not sure.

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

      reply	other threads:[~2011-01-18  9:50 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
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 [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=1295344242.2470.117.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