From: Andrew Morton <akpm@zip.com.au>
To: Robert Love <rml@tech9.net>
Cc: Ville Herva <vherva@niksula.hut.fi>,
James A Sutherland <jas88@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 07 Nov 2001 12:35:53 -0800 [thread overview]
Message-ID: <3BE99B29.354AA18A@zip.com.au> (raw)
In-Reply-To: <20011107213837.F26218@niksula.cs.hut.fi>, <E161UYR-0004S5-00@the-village.bc.nu> <E161Vbf-0000m9-00@lilac.csi.cam.ac.uk> <20011107213837.F26218@niksula.cs.hut.fi> <1005164667.884.5.camel@phantasy>
Robert Love wrote:
>
> On Wed, 2001-11-07 at 14:38, Ville Herva wrote:
> > A stupid question: does ext3 replay the journal before fsck? If not, the
> > inode errors would be expected...
>
> ext3 will reply the root file systems journal on boot when the kernel
> mounts root. other ext3 partitions will have their journals replayed
> when they are mounted.
>
> also, btw, I use RedHat 7.2 and fsck does not run if I don't hit Y. It
> is there for pedants or seriously screwed disks -- the journal replay
> should be sufficient.
>
fsck can perform journal replay. It's the same code, in fact.
So even if one does run fsck against an unclean ext3 partition,
fsck will just replay the journal and then exit. It won't do
the twenty minute go-grab-a-coffee thing unless it has explicitly
been passed the `-f' option. Doing that is very, very paraniod.
I normally just leave ext3 at the default check-time settings,
so fsck runs every thirtieth boot or so. ie: hourly :)
=
next prev parent reply other threads:[~2001-11-07 20:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 15:00 ext3 vs resiserfs vs xfs Roy Sigurd Karlsbakk
2001-11-07 15:23 ` Alan Cox
2001-11-07 15:28 ` Zvi Har'El
2001-11-07 20:19 ` Andreas Dilger
2001-11-07 21:11 ` Zvi Har'El
2001-11-07 21:25 ` Christian Bornträger
2001-11-07 21:45 ` Mike Fedyk
2001-11-07 21:42 ` Andreas Dilger
2001-11-07 22:11 ` arjan
2001-11-07 21:48 ` arjan
2001-11-08 7:08 ` Zvi Har'El
2001-11-08 11:06 ` Arjan van de Ven
2001-11-08 12:10 ` Zvi Har'El
2001-11-08 12:11 ` Arjan van de Ven
2001-11-08 11:35 ` ramfs leak Padraig Brady
2001-11-07 16:31 ` ext3 vs resiserfs vs xfs James A Sutherland
2001-11-07 19:38 ` Ville Herva
2001-11-07 19:50 ` Daniel Gryniewicz
2001-11-07 20:24 ` Robert Love
2001-11-07 20:35 ` Andrew Morton [this message]
2001-11-07 20:44 ` James A Sutherland
2001-11-07 21:11 ` Andreas Dilger
2001-11-07 21:37 ` ext3 vs resizerfs " Ville Herva
2001-11-07 21:45 ` Andreas Dilger
2001-11-08 0:13 ` ext3 vs resiserfs " James A Sutherland
2001-11-07 18:40 ` Anton Altaparmakov
2001-11-07 19:12 ` Alan Cox
2001-11-07 19:40 ` Anton Altaparmakov
2001-11-07 20:15 ` Andrew Morton
2001-11-07 21:33 ` Mike Fedyk
2001-11-07 22:00 ` Andrew Morton
2001-11-07 22:27 ` Mike Fedyk
2001-11-07 22:56 ` Andrew Morton
2001-11-07 23:18 ` Andreas Dilger
2001-11-07 22:52 ` Mike Fedyk
2001-11-07 22:59 ` Andrew Morton
2001-11-07 23:36 ` D. Stimits
2001-11-07 23:55 ` Mike Castle
2001-11-07 23:38 ` Mike Castle
2001-11-07 23:49 ` Mike Fedyk
2001-11-08 10:58 ` Juan Quintela
2001-11-07 20:25 ` Andreas Dilger
2001-11-07 23:33 ` Ryan Cumming
2001-11-09 16:11 ` Andreas Dilger
2001-11-07 20:36 ` Anton Altaparmakov
2001-11-07 20:21 ` Andreas Dilger
2001-11-07 20:27 ` Anton Altaparmakov
2001-11-07 20:05 ` Theodore Tso
2001-11-07 20:18 ` Andreas Dilger
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=3BE99B29.354AA18A@zip.com.au \
--to=akpm@zip.com.au \
--cc=jas88@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=vherva@niksula.hut.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.