Not sure if its of any use to you, but we had a similar situation and we are now looking at UBI (http://www.linux-mtd.infradead.org/doc/ubi.html). We use JFFS2 and we are considering using it over UBI. We had problems of data corruption in the flash so we now mount only partitions with writable data as RW. Rest of them remain RO and gets remounted as RW only when we want to write to it. Once written, we mount it RO again. Suresh On Wed, Jun 2, 2010 at 12:14 PM, Elvis Dowson <elvis.dowson@xxxxxxx> wrote: > > Hi, > I've got android-2.6.29 kernel and android-1.5r3 SDK version running on a gumstix Overo Earth (TI OMAP 3503), and I'm using the platform to implement a data logging application. > > The partition has been configured as read-write /dev/mtd4, with a merged rootfs and system folder. There are no separate /userdata and /cache partitions, all the rootfs, system, userdata and cache folders are on the /dev/mtd4 partition in rw mode. > > Now after 3 days of extended use and continuous writing, we suspect a potential corruption of the NAND device (a micron 256MB FLASH, 256MB RAM POP module). Has anyone else found micron NAND devices to get corrupted due to extended use? > > What options should I consider if I want to run my application from NAND and write data to the on-board NAND, and run the application reliably without corrupting the NAND device for at least 5 years? I am using the YAFFS2 filesystem. > > Best regards, > > Elvis Dowson > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
