I personally hate nand. I do embedded stuff all day long, and you spend more time dealing with NAND issues than anything else in the dev of a product. It not o

I personally hate nand. I do embedded stuff all day long, and you spend more time dealing with NAND issues than anything else in the dev of a product. It not only ship to you with bad blocks, but will fail if you write to it, it will also fail /by itself/ if left alone, so even a read-only filesystem is not safe, until you implement really paranoid duplication of pretty much everything. You can't JUST rely on ECC, you need to have duplication to allow the system to continue working; ECC will just tell you 'He's dead, Jim' and that doesn't help if you're a production device. Also, from my experience, newer NAND seems to nuke erase blocks by /bunches/ not just by units, so if you lose one, more often than not you love 8+ in a row. Also, the size of the erase blocks are getting bigger, so you lose a hell of a lot more every time you lose a block. Add the bloated file systems in linux (JFFS2 scan at mount time can be 30s easily!), and you end up wondering if it's really worth the trouble. These days I always propose using a micro-sd card (of quality) for any large storage need as it's a lot easier to replace, and a SPI NOR flash for the system if at all possible (it's horrendously slow to erase/write, but at least it's stable)