All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gryniewicz <dang@fprintf.net>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 7 Nov 2001 14:50:01 -0500	[thread overview]
Message-ID: <20011107145001.7f11aa56.dang@fprintf.net> (raw)
In-Reply-To: <20011107213837.F26218@niksula.cs.hut.fi>
In-Reply-To: <E161UYR-0004S5-00@the-village.bc.nu> <E161Vbf-0000m9-00@lilac.csi.cam.ac.uk> <20011107213837.F26218@niksula.cs.hut.fi>

FWIW, I run both ext3 and reiserfs on the same computer, and, after a crash, neither of them run fsck.  My ext3 partition is mounted on /, so maybe it matters that it's mounted *before* it's fscked?  The journal replay should mark it clean, so fsck should only run when it times out.  You can also set the fsck number to "0" in your fstab, and it will never fsck, but then you will loose the periodic fscks.  (I run 2.4.13-ac7-preempt-sse at the moment.)

Daniel
--- 
Recursion n.:
        See Recursion.
                        -- Random Shack Data Processing Dictionary


On Wed, 7 Nov 2001 21:38:37 +0200
Ville Herva <vherva@niksula.hut.fi> wrote:

> On Wed, Nov 07, 2001 at 04:31:24PM +0000, you [James A Sutherland] claimed:
> > 
> > Hm.. after a decidedly unclean shutdown, I decided to force an fsck here
> > and my ext3 partition DID have two inode errors on fsck... (Having said
> > that, the last entry in syslog was from the SCSI driver, and ext3's
> > journalling probably doesn't help much when the disk it's on goes AWOL...)
> 
> A stupid question: does ext3 replay the journal before fsck? If not, the
> inode errors would be expected...
> 
> 
> -- v --
> 
> v@iki.fi

  reply	other threads:[~2001-11-07 19:51 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 [this message]
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
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=20011107145001.7f11aa56.dang@fprintf.net \
    --to=dang@fprintf.net \
    --cc=linux-kernel@vger.kernel.org \
    --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.