linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Jón Benediktsson" <jonb@marel.is>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Handling power failure - MPC5200
Date: Thu, 04 Nov 2004 17:22:57 +0100	[thread overview]
Message-ID: <20041104162302.2B49DC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 04 Nov 2004 12:32:40 GMT." <OF368071C2.FBC6B7BC-ON00256F42.003F3DF3-00256F42.0044E8BB@marel.is>

In message <OF368071C2.FBC6B7BC-ON00256F42.003F3DF3-00256F42.0044E8BB@marel.is> you wrote:
> 
> Capacitors on the supply provide me with some milliseconds to repond to 
> power failure, which I would
> like to use to do as much cleanup as possible before power is totally 
> gone.  In particular, I am concerned

How many is "some"? If it's not >100 or so it is probably  not  worht
the effort...

> with trying to prevent damage to filesystems.  The board has Compact Flash
> and onboard flash which
> are used as filesystems.  The board will be used as an industrial 
> controller.
> 
> Can anyone point me to examples of how this can be handled ?

Use the standard methods: use the CF card read-only  (many  CF  cards
can  be  damaged  [beyond  repair]  when  you power off while a write
operation is in progress). Use a filesystem  on  the  ob-board  flash
which knows how to handle a loss of power (i. e., use JFFS2).

> Can anyone share experience of a similar setup, which filesystems to 
> select etc ?

We usually use ext2 read-only on the CF, JFFS2 for the writable parts
on the on-board flash, cramfs for all  parts  that  need  not  to  be
written  on  a  regular  base (most of your root filesystem including
application  code,  libraries  etc.),  and  a  FiST   based   overlay
filesystem in case of software patches need to be added.

Best regards,

Wolfgang Denk

-- 
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
You don't have to stay up nights to succeed; you have to  stay  awake
days.

  reply	other threads:[~2004-11-04 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 12:32 Handling power failure - MPC5200 Jón Benediktsson
2004-11-04 16:22 ` Wolfgang Denk [this message]
2004-11-05 14:13   ` Jón Benediktsson
2004-11-05 14:32     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 14:48 VanBaren, Gerald (AGRE)
2004-11-05 15:09 ` Mark Chambers
2004-11-05 20:47   ` Wolfgang Denk
2004-11-05 21:26     ` Mark Chambers
2004-11-06  0:52       ` Wolfgang Denk

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=20041104162302.2B49DC1430@atlas.denx.de \
    --to=wd@denx.de \
    --cc=jonb@marel.is \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).