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: Fri, 29 Aug 2003 11:09:57 -0700 [thread overview]
Message-ID: <20030829180957.GC27023@matchmail.com> (raw)
In-Reply-To: <20030829172451.GA27023@matchmail.com>
On Fri, Aug 29, 2003 at 10:24:51AM -0700, Mike Fedyk wrote:
> Hi,
>
> I have just converted my 25GB / partition from reiserfs to ext3 with 1k
> blocks, and now mutt is segfaulting periodocally.
>
> I suspect it is htree, because I left four mutt processes running last
> night, and two of them segfaulted.
>
> Interestingly enough, it happened about 1 minute apart, so they might have
> checked one of the large maildir folders and that could have caused the
> problem, except that the other two mutt processes should have checked the
> same folders, and they didn't crash.
>
> I have full strace output of each mutt process up until the segfault in two
> cases, and up until strace was stopped in the third case.
>
> Please let me know what more I can do to help track this down.
>
> I have tried this with:
> vmlinuz-2.6.0-test3-mm3
> vmlinuz-2.6.0-test4-mm1
>
How do I:
o Find out that a directory is using htree?
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?
Thanks,
Mike
next prev parent reply other threads:[~2003-08-29 18:09 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 [this message]
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
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=20030829180957.GC27023@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.