From: Theodore Tso <tytso@mit.edu>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 7 Nov 2001 15:05:24 -0500 [thread overview]
Message-ID: <20011107150524.A489@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0111071558090.29292-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0111071558090.29292-100000@mustard.heime.net>; from roy@karlsbakk.net on Wed, Nov 07, 2001 at 04:00:55PM +0100
On Wed, Nov 07, 2001 at 04:00:55PM +0100, Roy Sigurd Karlsbakk wrote:
> hi
>
> What's coolest/best/worst of ext3, ReiserFS and XFS?
> I just set up a RedHat 7.2 box with ext3, and after a few tests/chrashes,
> I see no difference at all. After a chrash, it really wants to run fsck
> anyway.
It will run fsck after a crash, but the fsck simply runs the journal
on ext3 filesystems that were uncleanly mounted. So the fsck will run
very quickly, *unless* the kernel had detected some kind of filesystem
error, and had set the "the filesystem has errors" flag, in which case
the full fsck check will be run.
If you're seeing a full fsck (i.e., a run which takes over a minute
and where you see the progress bar) after a crash consistently, you
might want to check and make sure that you've really converted the
filesystem in question to ext3.....
- Ted
next prev parent reply other threads:[~2001-11-07 21:26 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
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 [this message]
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=20011107150524.A489@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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.