From: Mark Hatle <fray@mvista.com>
To: Prakash kanthi <pkanthi@yahoo.com>
Cc: Jaap-Jan Boor <jjboor@lucent.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Flash File System Concerns
Date: Fri, 28 Mar 2003 11:20:57 -0600 [thread overview]
Message-ID: <3E848479.2030405@mvista.com> (raw)
In-Reply-To: <20030328171108.15068.qmail@web41213.mail.yahoo.com>
Prakash kanthi wrote:
> Folks,
>
> I have one concern regarding FFS. If you use flash for
> your entire filesystem including /var/log, /proc,
> etc.., you will be accessing flash too many times.
>
> And there is good chance that, your flash on the board
> reaches maximum number of accesses/writes limited by
> flash technology.
>
> How do people generally handle that in the industry.
> Especially, if you have on-board (non-replaceable)
> flash?
/proc is mounted from teh system and does not use flash.
Under the rules of the FHS, /var and /tmp should be mounted as a Read-Write
filesystem, the rest of the system (depending on options and distribution) can
be mounted Read-Only.
Now then, if you need things preserved between system reboots then you need to
have /var mounted on a "perminant" storage system. /tmp can be mounted w/ the
"tmpfs" filesystem. (Basically a ramdisk.)
The way that I generally recommend this stuff to customers is to symbolically
link /tmp to /var/tmp, mount /var as a tmpfs filesystem and then create the log,
spool, lock, etc directories as required for the system during the initscripts.
--Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-28 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E82F7F6.A1C684F@lucent.com>
2003-03-28 17:11 ` Flash File System Concerns Prakash kanthi
2003-03-28 17:20 ` Mark Hatle [this message]
2003-03-28 17:21 ` Gary D. Thomas
2003-03-28 22:13 ` Daris A Nevil
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=3E848479.2030405@mvista.com \
--to=fray@mvista.com \
--cc=jjboor@lucent.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pkanthi@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).