From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wf-out-1314.google.com ([209.85.200.170]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1JwWPu-0000YQ-CG for linux-mtd@lists.infradead.org; Thu, 15 May 2008 05:54:15 +0000 Received: by wf-out-1314.google.com with SMTP id 28so253254wfc.24 for ; Wed, 14 May 2008 22:54:12 -0700 (PDT) Message-ID: Date: Thu, 15 May 2008 13:54:12 +0800 From: Nancy To: "N Cheung" Subject: Re: [PATCH] [MTD] [UBI] add block device layer on top of UBI In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1204623622.23706.22.camel@sauron> <1204624414.23706.26.camel@sauron> <1210672391.5708.15.camel@sauron> Cc: linux-mtd List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, Norman On 5/15/08, N Cheung wrote: > Nancy and Artem, > > I want to run cramfs or squashfs on NAND. It looks like this ubiblock > may be the solution to my search. Or perhaps there is a NFTL layer > that manages bad blocks. Any suggestions? In my opinion, the Nand awared filesystem is the best choice for you. JFFS2, YAFFS2, UBIFS are all Nand awared filesystem. They are all run on Character device layer. UBI block device layer is creating for the traditional filesystem based on block device layer, such as FAT. Although UBI tolerant power failure, but that was not mean completely safe for FAT. Sometimes, FAT will turn to readonly if it detect an file EOF missing. In that case, you should use tool "dosfsck" to fix this problem. Maybe cramfs or squashfs may have the same problem like FAT has or other problem. To be safe, please use Nand awared filesystem instead. Use ubi block device layer when you have no other choices. -- Best wishes, Nancy