From: Doug McNaught <doug@mcnaught.org>
To: Daniel Pittman <daniel@rimspace.net>
Cc: linux-kernel@vger.kernel.org, "Buddy Lumpkin" <b.lumpkin@comcast.net>
Subject: Re: EXT intent logging
Date: Fri, 06 Aug 2004 09:22:38 -0400 [thread overview]
Message-ID: <87pt64o0yp.fsf@asmodeus.mcnaught.org> (raw)
In-Reply-To: <87zn58lhb1.fsf@enki.rimspace.net> (Daniel Pittman's message of "Fri, 06 Aug 2004 19:57:54 +1000")
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
next prev parent reply other threads:[~2004-08-06 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 4:55 EXT intent logging Buddy Lumpkin
2004-08-06 9:57 ` Daniel Pittman
2004-08-06 13:22 ` Doug McNaught [this message]
2004-08-06 16:36 ` Buddy Lumpkin
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=87pt64o0yp.fsf@asmodeus.mcnaught.org \
--to=doug@mcnaught.org \
--cc=b.lumpkin@comcast.net \
--cc=daniel@rimspace.net \
--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