From: Peter Stuge <peter@stuge.se>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] file system question
Date: Tue, 30 Mar 2010 15:53:30 +0200 [thread overview]
Message-ID: <20100330135330.12840.qmail@stuge.se> (raw)
In-Reply-To: <20100329184215.539920eb@osage.osagesoftware.com>
David Relson wrote:
> The device has a watchdog (recently activated) and during today's
> session it was triggered and wiped out my file system.
>
> Anybody have recommendations on which file system to use and the
> appropriate settings?
I would consider ext3. In order to deal with sudden resets (or power
loss) you really want a journalling filesystem. In that case you can
lose data (and need to check for, and handle, that on startup) but at
least the filesystem will be structurally ok.
Which filesystem to use on the flash module depends mostly on the
circumstances of systems in the field, such as how often they are
serviced, service personnel skill level and so on.
> Anybody have suggested readings so I can educate myself?
Hm, not so much. :\ The situation you're in is probably pretty
common, I have customers in the exact same situation, but it is very
different from what JFFS2, YAFFS and friends are made for, which is
that the filesystem actually has direct contact with the flash array.
Any kind of consumer level flash module, including disk-on-modules,
CF, SD, you name it, implements wear-levelling transparently. And
everyone considers their particular wear-levelling to be an important
competitive advantage, so they'll never give out details. The likes
of JFFS2, YAFFS require immediate addressing of NAND flash chips
connected to some bus, but that's never the case unless you're making
your own PCBs.
//Peter
next prev parent reply other threads:[~2010-03-30 14:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:42 [gentoo-embedded] file system question David Relson
2010-03-30 8:40 ` Ingo Krabbe
2010-03-30 11:47 ` David Relson
2010-03-30 12:17 ` Manuel Lauss
2010-03-30 14:01 ` Relson, David
2010-03-30 13:06 ` Karl Hiramoto
2010-03-30 13:28 ` Karl Hiramoto
2010-03-30 14:14 ` Arkadi Shishlov
2010-03-30 15:07 ` Karl Hiramoto
2010-03-30 16:29 ` Arkadi Shishlov
2010-03-30 14:19 ` Peter Stuge
2010-03-30 14:28 ` Arkadi Shishlov
2010-03-31 0:44 ` David Relson
2010-03-31 6:33 ` Arkadi Shishlov
2010-03-30 13:53 ` Peter Stuge [this message]
2010-03-30 14:36 ` Ed W
2010-03-30 18:11 ` wireless
2010-03-31 1:05 ` Peter Stuge
2010-04-01 16:48 ` Ed W
2010-03-31 9:26 ` Nebojša Ćosić
2010-03-31 11:30 ` David Relson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100330135330.12840.qmail@stuge.se \
--to=peter@stuge.se \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox