public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: mutt segfault with ext3 & 1k blocks & htree in 2.6
Date: Sat, 30 Aug 2003 16:58:19 -0700	[thread overview]
Message-ID: <20030830235819.GD898@matchmail.com> (raw)
In-Reply-To: <20030830131421.M15623@schatzie.adilger.int>

On Sat, Aug 30, 2003 at 01:14:21PM -0600, Andreas Dilger wrote:
> On Aug 29, 2003  11:09 -0700, Mike Fedyk wrote:
> > On Fri, Aug 29, 2003 at 10:24:51AM -0700, Mike Fedyk wrote:
> >  o Find out that a directory is using htree?
> 
> "lsattr <dir>" will show it.  Note that it will only ever be set on
> directories that are larger than a single disk block.
> 
> # lsattr -d d1
> ----------I-- d1
> 

Ok, now I only have htree enabled on one of my maildir folders.

> >  o Disable htree on my /?  (tune2fs -O ^dir_index), but then how do I get
> >    my directories back to non-htree without running fsck from a rescue CD?
> 
> That's the great thing about htree - you don't need to do anything to turn
> it off.  The on-disk format is exactly the same as without htree, and the
> first time you modify the directory it will clear the per-directory htree
> flag.

I'll do more testing to see if it fails only on that folder now.

But how do I re-enable htree on the directories (besides an fsck -D) in a
live system?

  reply	other threads:[~2003-08-30 23:58 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 [this message]
2003-08-31 22:44       ` Andreas Dilger
2003-09-01 20:27         ` Mike Fedyk
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=20030830235819.GD898@matchmail.com \
    --to=mfedyk@matchmail.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