mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Daniel Phillips <phillips@nl.linux.org>
Cc: adilger@turbolinux.com, linux-kernel@vger.kernel.org
Subject: Re: Ext2 Directory Index - File Structure
Date: Sun, 15 Apr 2001 19:42:05 -0600 (MDT)	[thread overview]
Message-ID: <200104160142.f3G1g6vx018717@webber.adilger.int> (raw)
In-Reply-To: <20010415195233Z92259-21887+33@humbolt.nl.linux.org> "from Daniel Phillips at Apr 15, 2001 09:52:33 pm"

Daniel, you write:
> Andreas, you wrote:
> > We should go with "EXT2_FEATURE_COMPAT_DIR_INDEX 0x0008"
> > because the on-disk layout is 100% compatible with older kernels, so
> > no reason to force read-only for those systems.  I'm guessing Ted had
> > put RO_COMPAT_BTREE_DIR in there in anticipation, but it was never used.
> 
> By the way, did you mean:
> 
> 	#define EXT2_FEATURE_COMPAT_DIR_INDEX 0x0002
> 
> since there is only one other COMPAT feature currently defined?

Quick note - you need to use 0x0008 or higher (Ted is the authority on
this).  The kernel ext2_fs.h is out of date compared to the one in e2fsprogs.
The EXT3_FEATURE_COMPAT_HAS_JOURNAL and EXT2_FEATURE_COMPAT_IMAGIC_INODES
is missing from the kernel header.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  reply	other threads:[~2001-04-16  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-15 19:52 Daniel Phillips
2001-04-16  1:42 ` Andreas Dilger [this message]
2001-04-16  6:58 ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2001-04-16 16:36 Daniel Phillips
2001-04-16 10:41 Daniel Phillips
2001-04-13 20:58 Daniel Phillips
2001-04-14  0:50 ` Andreas Dilger
2001-04-10 16:53 Daniel Phillips
2001-04-10 19: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=200104160142.f3G1g6vx018717@webber.adilger.int \
    --to=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@nl.linux.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

all inboxes | Powered by JetHome®