linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: rednoah <rednoax@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: why the emulated block driver by gluebi.c can't be used by FAT32
Date: Mon, 26 Jul 2010 07:11:26 +0300	[thread overview]
Message-ID: <1280117486.14917.3.camel@localhost> (raw)
In-Reply-To: <AANLkTinKvnAaLY8gGELXnQoDkUqmp2M30yNOqyNxK3pq@mail.gmail.com>

On Mon, 2010-07-26 at 12:02 +0800, rednoah wrote:
> Hi all:
>     According to the documentations of mtd,the gluebi of ubi is used to
> emulate block driver on the top of ubi

gluebi emulates an MTD device on top of an UBI volume. It does not
emulate a block device.

> ,for jffs2 or other mtd-oriented
> software using.Since the ubi is capable of wear leveling and bad
> block,why we can't build FAT32 filesystem on the emulated block
> device?
>     I tried building a FAT32 on a ubi volume using the emulated block
> node generated by gluebi.c.It seem ok when I transfer files between
> this
> partition and SD card.

I think you used UBI->gluebi->mtdblock->FAT. And this is bad because
mtdblock is bad - it loses data in case of power cuts. If you will never
have any power cuts, this setup may be ok, although very suboptimal in
terms of write speed.

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

      reply	other threads:[~2010-07-26  4:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26  4:02 why the emulated block driver by gluebi.c can't be used by FAT32 rednoah
2010-07-26  4:11 ` 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=1280117486.14917.3.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rednoax@gmail.com \
    /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).