linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mark gross <markgross@thegnar.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	markgross@thegnar.org,
	Raffaele Recalcati <lamiaposta71@gmail.com>,
	linux-pm@lists.linux-foundation.org,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] pm loss development
Date: Tue, 14 Jun 2011 07:06:42 -0700	[thread overview]
Message-ID: <20110614140642.GA14509@gvim.org> (raw)
In-Reply-To: <20110602222111.GA15414@ucw.cz>

On Fri, Jun 03, 2011 at 12:21:11AM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > What do you mean by safe state?
> > > >
> > > I need to get more details on this but I assume its a state where the
> > > meta data of the file system is committed to the emmc before lights go
> > > off such that when power is reapplied that the damage isn't too big. 
> > 
> > I don't think you can guarantee that the metadata won't be damaged
> > without notifying the filesystem of the event (and making it react
> > appropriately).
> 
> Journalling filesystem should survive power loss at random time, as
> long as block device behaves like a disk (i.e. writes whole sectors).
> 
> And that can be guaranteed at driver level...
> 

What if the battery falls out of the device at a bad time?  The HW will
have micro to mili seconds of time to close out whatever transaction is
in flight.

I know nothing about journalling file systems or how well they limit the
critical sections of time where the file system is exposed to corruption
from sudden power failure.  Its an interesting question though.

--mark


  reply	other threads:[~2011-06-14 14:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 17:11 pm loss development Raffaele Recalcati
2011-05-12 17:11 ` [PATCH 1/4] export bus_kset Raffaele Recalcati
2011-05-12 19:28   ` Rafael J. Wysocki
2011-05-13 17:11     ` Davide Ciminaghi
2011-05-15 14:13       ` [linux-pm] " Davide Ciminaghi
2011-05-17 23:04         ` Rafael J. Wysocki
2011-05-12 17:11 ` [PATCH 2/4] PM / Loss: power loss management Raffaele Recalcati
2011-05-12 19:57   ` Rafael J. Wysocki
2011-05-13 13:02     ` Davide Ciminaghi
2011-05-17 23:32       ` Rafael J. Wysocki
2011-05-19  9:26         ` Davide Ciminaghi
2011-05-19 14:25           ` [linux-pm] " Alan Stern
2011-05-19 20:52             ` Rafael J. Wysocki
2011-05-12 17:11 ` [PATCH 3/4] mmc: bus and block device drivers: support for pm_loss Raffaele Recalcati
2011-05-12 17:11 ` [PATCH 4/4] DaVinci: vpfe: " Raffaele Recalcati
2011-05-12 19:27 ` pm loss development Rafael J. Wysocki
2011-05-13  6:39   ` Raffaele Recalcati
2011-05-13 16:54     ` Rafael J. Wysocki
2011-05-14 16:35       ` [linux-pm] " mark gross
2011-05-17 23:07         ` Rafael J. Wysocki
2011-05-18  3:12           ` mark gross
2011-05-18 19:43             ` Rafael J. Wysocki
2011-05-18 22:17               ` Mark Brown
2011-05-19 12:45               ` mark gross
2011-06-02 22:21               ` Pavel Machek
2011-06-14 14:06                 ` mark gross [this message]
2011-06-14 14:36                   ` Alan Cox
2011-05-14 20:21       ` Raffaele Recalcati
2011-05-17 23:10         ` Rafael J. Wysocki
2011-05-14 18:53   ` [linux-pm] " Oliver Neukum
2011-05-14 20:34     ` Raffaele Recalcati
2011-05-17 23:06       ` Rafael J. Wysocki
2011-05-14 16:24 ` mark gross
2011-05-14 20:30   ` Raffaele Recalcati
2011-05-14 23:33     ` mark gross

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=20110614140642.GA14509@gvim.org \
    --to=markgross@thegnar.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=lamiaposta71@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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).