public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>, Andrew Morton <akpm@osdl.org>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Get rid of extents mount option - try 2
Date: Wed, 11 Oct 2006 11:16:38 -0600	[thread overview]
Message-ID: <20061011171638.GP22010@schatzie.adilger.int> (raw)
In-Reply-To: <1160169700.8658.56.camel@kleikamp.austin.ibm.com>

On Oct 06, 2006  16:21 -0500, Dave Kleikamp wrote:
> EXT4: Get rid of extents mount option
> 
> Enabling an ext4 file system to use extents should be done with
> 'tune2fs -O extents' or 'mke2fs -O extents', not with a mount option

I would agree that the presence of INCOMPAT_EXTENTS should imply the
EXTENTS mount option, but it is also desirable to be able to turn this
off for testing.  In our internal patches we also have a "noextents"
mount option to disable extents at runtime even if "extents" was given
as a default mount option.

So, I would leave most of the code as-is (with "test_opt(sb, EXTENTS)"),
and just have ext3_fill_super() enable EXT4_MOUNT_EXTENTS if
INCOMPAT_EXTENTS is set.  This is a tiny bit tricky since parse_options()
is called before the superblock is read, so I suspect we'll need a
separate EXT4_MOUNT_NOEXTENTS to distinguish between no mount "extents"
option given and "noextents" disabling this.

The Opt_noextents handling would clear EXT4_MOUNT_EXTENTS, and vice versa.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


  parent reply	other threads:[~2006-10-11 17:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 18:23 Updated ext4/jbd2 patches based on 2.6.19-rc1 Dave Kleikamp
2006-10-05 20:19 ` Andrew Morton
2006-10-05 23:25   ` Linus Torvalds
2006-10-06 12:50     ` Dave Kleikamp
2006-10-06 16:11       ` Linus Torvalds
2006-10-05 21:59 ` Andrew Morton
2006-10-06  0:39 ` Andrew Morton
2006-10-10  6:29   ` Andrew Morton
2006-10-10  7:54     ` Suparna Bhattacharya
2006-10-10  8:14       ` Andrew Morton
2006-10-10 20:02         ` [RFC] [PATCH] Documentation/filesystems/ext4.txt Dave Kleikamp
2006-10-10 20:56           ` Andrew Morton
2006-10-11 17:03           ` Andreas Dilger
2006-10-12 14:18           ` Valerie Clement
2006-10-06  3:55 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06  3:58   ` Andrew Morton
2006-10-06 10:34     ` Alex Tomas
2006-10-06  4:54   ` Randy Dunlap
2006-10-06  5:05     ` Andrew Morton
2006-10-06  5:53     ` Andreas Dilger
2006-10-06  6:04       ` Andrew Morton
2006-10-06  6:41         ` Andreas Dilger
2006-10-06  6:50           ` Andrew Morton
2006-10-06 10:31             ` Alex Tomas
2006-10-06 13:57               ` Andrew Morton
2006-10-07 20:09                 ` alex
2006-10-06  6:52           ` Suparna Bhattacharya
2006-10-06 12:21   ` Theodore Tso
2006-10-06 21:10     ` [PATCH] Get rid of extents mount option Dave Kleikamp
2006-10-06 21:21       ` [PATCH] Get rid of extents mount option - try 2 Dave Kleikamp
2006-10-06 22:32         ` Andrew Morton
2006-10-06 23:20           ` Dave Kleikamp
2006-10-07  4:14             ` Theodore Tso
2006-10-07 15:53               ` Dave Kleikamp
2006-10-07 17:20                 ` Theodore Tso
2006-10-07 19:45                   ` Alex Tomas
2006-10-07 19:57                   ` Andrew Morton
2006-10-10 18:48                   ` Dave Kleikamp
2006-10-10 21:07                     ` Theodore Tso
2006-10-10 21:18                       ` Andrew Morton
2006-10-11 17:16         ` Andreas Dilger [this message]
2006-10-06  4:31 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06  5:58   ` Andreas Dilger
2006-10-06  6:10     ` Andrew Morton
2006-10-06  6:48       ` 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=20061011171638.GP22010@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shaggy@austin.ibm.com \
    --cc=tytso@mit.edu \
    /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