All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 07 Nov 2001 14:59:20 -0800	[thread overview]
Message-ID: <3BE9BCC8.925A1234@zip.com.au> (raw)
In-Reply-To: <E161Y87-00052r-00@the-village.bc.nu>, <5.1.0.14.2.20011107183639.0285a7e0@pop.cus.cam.ac.uk> <5.1.0.14.2.20011107193045.02b07f78@pop.cus.cam.ac.uk> <3BE99650.70AF640E@zip.com.au>, <3BE99650.70AF640E@zip.com.au> <20011107133301.C20245@mikef-linux.matchmail.com> <3BE9AF15.50524856@zip.com.au>, <3BE9AF15.50524856@zip.com.au> <20011107145229.A560@mikef-linux.matchmail.com>

Mike Fedyk wrote:
> 
> On Wed, Nov 07, 2001 at 02:00:53PM -0800, Andrew Morton wrote:
> > Mike Fedyk wrote:
> > >
> > > I have a switch "data=journal" that ext2 will choke on when I boot into an
> > > ext2 only kernel.
> > >
> > > Is there another way to change the journaling mode besides modifying
> > > /etc/fstab?
> >
> > Try  adding `rootflags=data=journal' to your kernel boot
> > commandline.
> >
> 
> Oh, JOY!
> 
> adding that line to an ext2 only kernel will make it kernel panic when it
> tries to mount root because it doesn't understand the option!
> 

It's dumb that an unrecognised option be a fatal error.  Same
problem with modules, actually.  If you add a new module option
to modules.conf and then go back to an older kernel your module
won't load (here's where kaos pokes me with the rtfm stick).

You can create a second entry in lilo.conf which refers to the same
kernel image, but which doesn't have the rootflags option.

-

  reply	other threads:[~2001-11-07 23:04 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 [this message]
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=3BE9BCC8.925A1234@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    /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.