All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: "Zvi Har'El" <rl@math.technion.ac.il>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	linux-kernel@vger.kernel.org, nyh@math.technion.ac.il
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 7 Nov 2001 14:42:31 -0700	[thread overview]
Message-ID: <20011107144231.M5922@lynx.no> (raw)
In-Reply-To: <20011107131930.H5922@lynx.no> <Pine.GSO.4.33.0111072302460.12525-100000@leeor.math.technion.ac.il>
In-Reply-To: <Pine.GSO.4.33.0111072302460.12525-100000@leeor.math.technion.ac.il>; from rl@math.technion.ac.il on Wed, Nov 07, 2001 at 11:11:59PM +0200

On Nov 07, 2001  23:11 +0200, Zvi Har'El wrote:
> On Wed, 7 Nov 2001, Andreas Dilger wrote:
> > Are you SURE you are using ext3?  Check /proc/mounts to be sure.  What it
> > says in /etc/fstab is irrelevant for the root filesystem.
> >
> /proc/mounts has
> 
> /dev/root / ext2 rw 0 0
> /dev/hda6 /home ext3 rw 0 0
> 
> However, tune2fs -l on both /dev/hda1 (the root filesystem) and /dev/hda6
> Filesystem features:      has_journal sparse_super
> 
> 
> How do  fix the situation at this stage? I am using Redhat 7.2 with kernel
> 2.4.9-13

Do you have ext3 compiled into the kernel?  I suspect you have it as a module.

Also, given the large number of similar bug reports, maybe RedHat has a bug in
their mkinitrd script which doesn't try to mount the root fs with ext3?  I
don't know enough about their mkinitrd tools to say - Alan, Stephen?

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  parent reply	other threads:[~2001-11-07 21:44 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 [this message]
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
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=20011107144231.M5922@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nyh@math.technion.ac.il \
    --cc=rl@math.technion.ac.il \
    --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.