public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: t kevin <kevint324@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question about ubiformat and how to better use UBIFS
Date: Mon, 08 Sep 2014 14:43:59 +0300	[thread overview]
Message-ID: <1410176639.10764.157.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAOx4H9BopH3F5xwmQ-B5AckTS65SUss_mxjWi2N6ibXovnm61g@mail.gmail.com>

On Thu, 2014-09-04 at 20:17 +0800, t kevin wrote:
> So here are my questions.
> 1. (Generally speaking) Which one is better? I know ubiformat is going
> to erase every PEB  so right now I prefer the second approach since I
> don't have to do ubiformat everytime. It sounds like the erase counter
> grows slower.

If the second way works for you, you may stick to it.

Back when I was working in Nokia, where we had to flash newly produced
devices in the factory pipeline, we had to have a flash-able image. So
we used the mkfs.ubifs approach.

So generally, the mkfs.ubifs approach was designed for real production,
and the mount approach was originally supported just to make developers'
life easier.

But use whatever is better for your needs.

> 2. I'm working on an embedded device which has limited CPU power so
> I'd like to use compressed_method=none. It can be done by passing -x
> none to mkfs.ubifs. But I don't see similar option in ubiformat or
> ubimkvol.

Well, there is no compression involved in the UBI level, and both of
these tools work on the UBI level, they do not know anything about
UBIFS. That's why you do not see this option.

>  So when I go to the 2nd approach the mounted rootfs is
> always compressed.

Use 'mount -o compr=none', check Documentation/filesystems/ubifs.txt.

> http://www.linux-mtd.infradead.org/faq/ubifs.html#L_comproff
> This method is not helping much. I want to disable compression on the
> entire fs, just like mkfs.ubifs -x none did.

Yeah, that section misses -o compre=none. I've just fixed it up, thanks!

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2014-09-08 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 12:17 Question about ubiformat and how to better use UBIFS t kevin
2014-09-08 11:43 ` Artem Bityutskiy [this message]
2014-09-09  8:23 ` Konstantin Tokarev

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=1410176639.10764.157.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=kevint324@gmail.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