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: Heusden@mail.bonn-fries.net, Folkert van <f.v.heusden@ftr.nl>,
	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: Mon, 25 Jun 2001 18:10:50 +0200	[thread overview]
Message-ID: <01062518105001.01008@starship> (raw)
In-Reply-To: <0105311813431J.06233@starship> <01062018584308.00439@starship> <993462395.9593.0.camel@syntax.dera.gov.uk>
In-Reply-To: <993462395.9593.0.camel@syntax.dera.gov.uk>

On Monday 25 June 2001 11:46, Tony Gale wrote:
> After some testing, removing the grsecurity patch seems to have solved
> the disappearing-free-space problem. Now just need to find out why.
>
> On 20 Jun 2001 18:58:43 +0200, Daniel Phillips wrote:
> > 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.
>
> It was a test partition, just happended to be a root one. AFAIAA, isn't
> the fact that the file format may change irrelevant. You want people to
> test this stuff or not? If it's not tested on a root fs then how do you
> know there won't be any problems.
>
> Sorry, but when someone reports a problem, and then you say, well don't
> test it like that then, it is really not acceptable.

Sure, if your root partition is expendable, by all means go ahead.  Ted has 
already offered to start the required changes to e2fsck, which reminds me, I 
have to send the promised docs.  For now, just use normal fsck and it will 
(in theory) turn the directory indexes back into normal file blocks, and have 
no effect on inodes.  Lets take advantage of the opportunity to test that 
feature.  The new improved e2fsck should be capable of re-adding the indexes, 
so we'll get to test that too ;-)

Lets continue this privately and see what's going on with your inode leak.

--
Daniel

  reply	other threads:[~2001-06-25 16:08 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
2001-06-25  9:46     ` Tony Gale
2001-06-25 16:10       ` Daniel Phillips [this message]
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=01062518105001.01008@starship \
    --to=phillips@bonn-fries.net \
    --cc=Heusden@mail.bonn-fries.net \
    --cc=adilger@turbolinux.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=f.v.heusden@ftr.nl \
    --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