mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Buddy Lumpkin" <b.lumpkin@comcast.net>
To: "'Doug McNaught'" <doug@mcnaught.org>,
	"'Daniel Pittman'" <daniel@rimspace.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: EXT intent logging
Date: Fri, 6 Aug 2004 09:36:08 -0700	[thread overview]
Message-ID: <S268180AbUHFQey/20040806163555Z+829@vger.kernel.org> (raw)
In-Reply-To: <87pt64o0yp.fsf@asmodeus.mcnaught.org>

But if it doesn't do writes to the journal first, how does it identify
transactions that were "in flight" when the system went down to reverse
them? How do you catch a parial update to an inode for instance?

--Buddy

-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Doug McNaught
Sent: Friday, August 06, 2004 6:23 AM
To: Daniel Pittman
Cc: linux-kernel@vger.kernel.org; Buddy Lumpkin
Subject: Re: EXT intent logging

Daniel Pittman <daniel@rimspace.net> writes:

> What is normal is that ext3 will perform an *occasional* fsck - by
> default, once a month or every thirty-odd mounts - to catch any
> corruption that has been missed by the journaling.

And if you don't want this to happen, you can use 'tunefs' to turn it
off, and rely entirely on journal replays.

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863
-
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/


  reply	other threads:[~2004-08-06 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  4:55 Buddy Lumpkin
2004-08-06  9:57 ` Daniel Pittman
2004-08-06 13:22   ` Doug McNaught
2004-08-06 16:36     ` Buddy Lumpkin [this message]
2004-08-06 18:46       ` Bernd Eckenfels
2004-08-06 19:56 ` Theodore Ts'o
2004-08-07  4:50   ` Buddy Lumpkin
2004-08-08  1:54   ` Thomas Zimmerman

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=S268180AbUHFQey/20040806163555Z+829@vger.kernel.org \
    --to=b.lumpkin@comcast.net \
    --cc=daniel@rimspace.net \
    --cc=doug@mcnaught.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®