linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: linux-ext4@vger.kernel.org
Subject: Re: Autoremoval of test_fs flag kinda sucks
Date: Sun, 21 Dec 2008 21:28:15 -0500	[thread overview]
Message-ID: <20081222022815.GD23723@mit.edu> (raw)
In-Reply-To: <20081221134326.GA26216@nineveh.local>

On Sun, Dec 21, 2008 at 08:43:27AM -0500, Joseph Fannin wrote:
> This is mostly me blowing off a little steam here, so yeah.  But maybe
> it won't hurt to send out a heads up and get this in the archives:
> 
> Booting a 2.6.28-pre kernel will cause e2fsck to remove the test_fs
> flag from any filesystem it checks, presumably because "ext4dev" has
> become "ext4" in 2.6.28.  If your root fs is on ext4, this makes it
> impossible to reboot back into a older kernel (i.e. < 2.6.28) since it
> will refuse to mount an ext4dev fs without the "test_fs" flag set --
> unless you chase after e2fsck and set the flag back.

Yeah, Sorry I guess I didn't think it was going to be *that* common
for people to be going back and forth between the boundary.  It is
possible to disable this, BTW, via /etc/e2fsck.conf:

[options]
	clear_test_fs_flag = false

The assumption I made was that the number of pre-2.6.28 ext4 users
would be small, and so it would be safe to default the option to true.

      	 	       	  	   	- Ted

  reply	other threads:[~2008-12-22  2:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 13:43 Autoremoval of test_fs flag kinda sucks Joseph Fannin
2008-12-22  2:28 ` Theodore Tso [this message]
2009-02-12 16:43   ` Joseph Fannin

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=20081222022815.GD23723@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).