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: Tue, 2 Sep 2003 14:58:39 -0700 [thread overview]
Message-ID: <20030902215839.GC13684@matchmail.com> (raw)
In-Reply-To: <20030902100927.T15623@schatzie.adilger.int>
On Tue, Sep 02, 2003 at 10:09:27AM -0600, Andreas Dilger wrote:
> Normally an application segfault is really caused by a kernel OOPS, so if
> you look into your syslog file or dmesg output you should see an oops.
>
No, I'm not seeing any oopses on this machine at all right now (not that I
couldn't cause a couple at will, but those are reported with varying degrees
of success on getting fixes)
> > And now mutt is segfaulting on non-htree directories too.
>
> I couldn't comment on that, but either the directories are somehow corrupted
> (e2fsck will know), or the problem is related either to 1kB blocks or not
> related to the filesystem at all.
Ok, I will convert my ext3 (cp twice) to 4k blocks, and try to reproduce.
Hopefully I didn't hit a library update (in debian a mixed debian testing
/ unstable system) that caused this problem.
next prev parent reply other threads:[~2003-09-02 21: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
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 [this message]
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=20030902215839.GC13684@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.