public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mutt segfault with ext3 & 1k blocks & htree in 2.6
Date: Mon, 1 Sep 2003 13:27:29 -0700	[thread overview]
Message-ID: <20030901202729.GB31760@matchmail.com> (raw)
In-Reply-To: <20030831164448.O15623@schatzie.adilger.int>

On Sun, Aug 31, 2003 at 04:44:48PM -0600, Andreas Dilger wrote:
> On Aug 30, 2003  16:58 -0700, Mike Fedyk wrote:
> > But how do I re-enable htree on the directories (besides an fsck -D) in a
> > live system?
> 
> You need to re-enable the dir_index feature, and then for directories which
> are larger than a block in size you need something like:
> 
> 	mkdir new_dir
> 	mv old_dir/* new_dir
> 	rmdir old_dir
> 	mv new_dir old_dir
> 
> The new directory will have htree enabled because it started out at 1 block
> in size.

Ok I ended up doing this after a little thought.  Thanks.

But I am seeing segfaults in mutt under 2.6 ext3 with 1k blocks, that I
don't see in 2.4, and didn't see under reiserfs.  I can try with 4k blocks,
if you'd like, is there anything I can do to capture more information that
could be happening to cause this?

And now mutt is segfaulting on non-htree directories too.

  reply	other threads:[~2003-09-01 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 17:24 mutt segfault with ext3 & 1k blocks & htree in 2.6 Mike Fedyk
2003-08-29 18:09 ` Mike Fedyk
2003-08-30 19:14   ` Andreas Dilger
2003-08-30 23:58     ` Mike Fedyk
2003-08-31 22:44       ` Andreas Dilger
2003-09-01 20:27         ` Mike Fedyk [this message]
2003-09-02 16:09           ` Andreas Dilger
2003-09-02 21:58             ` Mike Fedyk
2003-08-29 18:33 ` Andy Isaacson
2003-08-29 19:00   ` Mike Fedyk

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=20030901202729.GB31760@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@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