All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Ryan Cumming <bodnar42@phalynx.dhs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Fri, 9 Nov 2001 09:11:40 -0700	[thread overview]
Message-ID: <20011109091140.A1778@lynx.no> (raw)
In-Reply-To: <5.1.0.14.2.20011107183639.0285a7e0@pop.cus.cam.ac.uk> <5.1.0.14.2.20011107193045.02b07f78@pop.cus.cam.ac.uk> <20011107132552.J5922@lynx.no> <E161cCh-0003de-00@localhost>
In-Reply-To: <E161cCh-0003de-00@localhost>; from bodnar42@phalynx.dhs.org on Wed, Nov 07, 2001 at 03:33:54PM -0800

On Nov 07, 2001  15:33 -0800, Ryan Cumming wrote:
> On November 7, 2001 12:25, Andreas Dilger wrote:
> > If both ext2 and ext3 are compiled into the kernel, then ext3 will try
> > first to mount the root fs.  If there is no journal on this fs (check this
> > with tune2fs -l <dev>, and look for "has_journal" feature), then it will be
> > mounted as ext2.  If you are doing strange things with initrd and modules,
> 
> Is there any particular reason why the ext3 driver can't handle mounting both 
> ext2 and ext3 filesystems? 

Not really - just an implementation issue.  At one point (long ago) I had
started putting in support for this.  However, the consensus is that some
people will still want to use the less complex ext2 code instead of ext3
that pretends to be ext2.  I imagine that eventually support for mounting
unjournaled ext2 filesystems with the ext3 driver will be added, but there
is no pressing need - you can always use the ext2 driver.  Yes, it takes
a bit more memory to have both loaded, but most people who switch to ext3
don't use ext2 filesystems anymore anyways.

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


  reply	other threads:[~2001-11-09 16:12 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 [this message]
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=20011109091140.A1778@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=bodnar42@phalynx.dhs.org \
    --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 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.