[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110614140642.GA14509@gvim.org>
Date: Tue, 14 Jun 2011 07:06:42 -0700
From: mark gross <markgross@...gnar.org>
To: Pavel Machek <pavel@....cz>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, markgross@...gnar.org,
Raffaele Recalcati <lamiaposta71@...il.com>,
linux-pm@...ts.linux-foundation.org,
davinci-linux-open-source@...ux.davincidsp.com,
linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] pm loss development
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists