Comment 4 for bug 900923

On Tue, Dec 06, 2011 at 09:39:48PM -0000, Colin King wrote:
> Hi Steve, I will re-rerun journal-commit on an idle system tomorrow and
> get back to you. Any ideas of scenarios that are typical and may
> generate typical I/O patterns?

I'd guess that typical patterns would include playing music via the default
music player, viewing static web pages, and viewing flash videos in a web
browser. (Other common scenarios when on battery might be composing email /
docs, but I guess those are harder to script for testing?)

> As for the 600 second setting, it is a little scary to see it set so
> high and cause potential data loss risk. But, that's kinda incidental.

Provided that we're using data=ordered (we are, aren't we? :-), I don't find
the prospect of 10 minutes of data loss while on battery terrifying,
especially provided there are syncs happening at sensible times (e.g.,
before suspending/hibernating?). And if it buys more battery life, the odds
of an unplanned power event go down, which seems like a win for data
integrity anyway.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>