lkml.org 
[lkml]   [2001]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ext3: kjournald and spun-down disks
On Sun, 25 Nov 2001, Andrew Morton wrote:

> Oliver Xymoron wrote:
> >
> > Ok, so what's the theory behind the journal timer? Why would we want
> > ext3 journal flushed more or less often than ext2 metadata given that
> > they're of equivalent importance?
>
> umm, err.. If your machine crashes, ext3 will restore its state
> to that which pertained between zero and five seconds before the crash.
>
> With ext2+fsck, things are not as clear. Your data will be restored
> to that which pertained from zero to thirty seconds prior to crash.

And that's my point exactly. In terms of integrity, each timer serves the
same purpose - get the filesystem on disk in sync with what's in memory.
Obviously ext3 does a better job of this than ext2 in terms of recovering
from partial transactions, but in both cases the flush is accomplishing
the same thing. I can see no a priori reason why the ext3 journal flush
would be timed differently than ext2 journal flush. If the flush time for
ext3 should be shorter, then so should the time for everything else. See?

--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.063 / U:1.120 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site