From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com) by bombadil.infradead.org with esmtps (Exim 4.72 #1 (Red Hat Linux)) id 1OdF31-0004Yf-QH for linux-mtd@lists.infradead.org; Mon, 26 Jul 2010 04:12:16 +0000 Subject: Re: why the emulated block driver by gluebi.c can't be used by FAT32 From: Artem Bityutskiy To: rednoah In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 26 Jul 2010 07:11:26 +0300 Message-ID: <1280117486.14917.3.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: linux-mtd@lists.infradead.org Reply-To: dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 (Артём Битюцкий)