public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Tony Gale <gale@syntax.dera.gov.uk>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
	Alexander Viro <viro@math.psu.edu>,
	Andreas Dilger <adilger@turbolinux.com>
Subject: Re: [UPDATE] Directory index for ext2
Date: Wed, 20 Jun 2001 18:58:43 +0200	[thread overview]
Message-ID: <01062018584308.00439@starship> (raw)
In-Reply-To: <0105311813431J.06233@starship> <993049198.3089.2.camel@syntax.dera.gov.uk>
In-Reply-To: <993049198.3089.2.camel@syntax.dera.gov.uk>

On Wednesday 20 June 2001 16:59, Tony Gale wrote:
> The main problem I have with this is that e2fsck doesn't know how to
> deal with it - at least I haven't found a version that will. This makes
> it rather difficult to use, especially for your root fs.

Good, the file format isn't finalized, this is only recommended for use on a 
test partition.

> And, since I used it, and have since stopped using it, I have a problem
> in what all my disk free space disappears over a couple of days - I have
> to run fsck to recover it, were it appears as deleted inodes with zero
> dtime. I can't say for sure that the dir index stuff is at fault though.

It could well be, I'd appreciate any more data you have on that.

> I am currently using 2.4.6-pre3 without the dir patch installed. I am
> using the grsecurity patch though.
>
> I have just upgraded to e2fsprogs-1.21 in the hope of sorting it out. If
> that fails I'll revert to a clean 2.4.6-pre kernel. Other ideas welcome.
>
> -tony
>
> On 31 May 2001 18:13:43 +0200, Daniel Phillips wrote:
> > Changes:
> >
> >   - Freshen to 2.4.5
> >   - EXT2_FEATURE_COMPAT_DIR_INDEX flag finalized
> >   - Break up ext2_add_entry for aesthetic reasons (Al Viro)
> >   - Handle more than 64K directories per directory (Andreas Dilger)
> >   - Bug fix: new inode no longer inherits index flag (Andreas Dilger)
> >   - Bug fix: correct handling of error on index create (Al Viro)
> >
> > To-Do:
> >
> >   - More factoring of ext2_add_entry
> >   - Fall back to linear search in case of corrupted index
> >   - Finalize hash function

  parent reply	other threads:[~2001-06-20 16:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 16:13 [UPDATE] Directory index for ext2 Daniel Phillips
2001-05-31 19:44 ` [Ext2-devel] " Andreas Dilger
2001-05-31 21:02   ` Daniel Phillips
2001-05-31 22:42     ` Andreas Dilger
2001-06-03  0:19   ` Daniel Phillips
2001-06-20 14:59 ` Tony Gale
2001-06-20 16:02   ` [Ext2-devel] " Theodore Tso
2001-06-20 17:27     ` Daniel Phillips
2001-06-20 16:58   ` Daniel Phillips [this message]
2001-06-25  9:46     ` Tony Gale
2001-06-25 16:10       ` Daniel Phillips
2001-06-25 19:51         ` [Ext2-devel] " Andreas Dilger
2001-06-25 22:25           ` Daniel Phillips
2001-06-26  9:27             ` Tony Gale
2001-06-26 23:49             ` Theodore Tso
2001-06-27  0:08               ` [RFC] Checks in ext2_new_block() Alexander Viro
2001-07-03 10:00               ` [Ext2-devel] Re: [UPDATE] Directory index for ext2 Tony Gale

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=01062018584308.00439@starship \
    --to=phillips@bonn-fries.net \
    --cc=adilger@turbolinux.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=gale@syntax.dera.gov.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.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