On 8/24/11 07:55 , Michael Sierchio wrote: > If you *must* mount a CF-backed filesystem read-write, you do want to > minimize writes. Mount it rw,noatime. Use fifolog for logging and > the like. Don't use an ext3 filesystem, or any other logging > filesystem - the logging and metadata writes are counterproductive > when the medium has a limited write lifespan. I'd use UFS1, frankly.
I had SLC NAND CF cards with ufs+softupdates writing logs in the field for years. failures are trivially more infrequent than with fujitsu industrial 2.5"drives. the cf cards (still in use) were manufactured by transcend in 2007/2008 > - M > > On Tue, Aug 23, 2011 at 6:58 AM, Matt Ryanczak <[email protected]> wrote: >> The quality of CF cards varies greatly. I suggest trying another card. >> Industrial grade cards from sandisk, emphase or similar have the highest >> write cycle count. >> >> Also look in to non-journaled file systems or disable journaling on your >> fs of choice to increase life. Disabling atime (using relatime or >> noatime) can help too. Ofcourse the effects of all of this depends on >> the specific cards wear leveling implementation (if it has one) and >> over-all quality. >> >> I've had good luck with sandisk industrial or professional grade CF >> cards. Some of which have run for years with out problems. >> >> ~Matt >> >> On 8/23/11 9:01 AM, Embedding Linux wrote: >>> Hello, >>> >>> We got our net5501 up and running on Gentoo Linux, with a few troubles >>> here and there. >>> >>> But we are getting filesystem corruption errors quite quickly, even >>> without significant fs activity. Error is usually >>> "htree_dirblock_to_tree: bad entry in directory #xxxx", but we begin to >>> get "ext3_lookup: deleted inode referenced xxxx" errors too. >>> >>> The CF card has been taken off the net5501, fsck-ed (lots of FS >>> problems), put back in the net5501 and booted again... Half a day later, >>> the errors do creep back. >>> >>> We have (not yet) tried changing the CF card. >>> >>> We're using an ext3 filesystem on the CF card. Is it a good choice ? Do >>> anyone has some idea as to what could cause those errors, and how to get >>> rid of them ? >>> >>> Tia, >> >> _______________________________________________ >> Soekris-tech mailing list >> [email protected] >> http://lists.soekris.com/mailman/listinfo/soekris-tech >> > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
