Hello linux-mtd, -embedded and -fsdevel, There are a lot of actively developed block filesystems out there, more than flash filesystems. Read-only block FS can run with great perfs on flash supports with the mtdblock interface (eg. SquashFS) but since it doesn't handle bad blocks, read will fail when you hit one. That's why we are considering the pros and cons of having a block interface on top of UBI: UBI takes care of bad blocks and filesystems above it don't have to worry about them. An option could be to implement bad block handling in mtdblock but then, there wouldn't be any wear-leveling. In case of read-only filesystems, wear-leveling is not so important but when read-only and read-write filesystems coexist, static wear-leveling is important. And I understand that UBI implements static wear-leveling. So it would make sense to have a block read-only filesystem on top of UBI along with a ubifs read-write filesystem. So, what do you think about that possibility ? Do you see alternative approaches or other ways to address the problem of using read-only oriented filesystems on flash (w/o reinventing the wheel) ? Regards, David. -- David Wagner, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
