public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: linux-ext4@vger.kernel.org
Subject: e2fsck -D segfaults in pass 3A
Date: Thu, 13 Mar 2008 21:23:19 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803132116430.7433@sheep.housecafe.de> (raw)

After playing around with e2fsck (today's git of the "pu" branch) a bit 
more, I still cannot use -D on this filesystem. I've tried with earlier 
version, but it still dumps core in pass 3A (Optimizing directories). I've 
compiled e2fsprogs with "CFLAGS="-g" ./configure --enable-htree; make", 
too get a few more results when this happens. Running under gdb gives:

(gdb) run -Dfv /dev/md4
Starting program: /opt/e2fsprogs/sbin/e2fsck -Dfv /dev/md4
e2fsck 1.40.7 (28-Feb-2008)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories

Program received signal SIGSEGV, Segmentation fault.
0x08065bb9 in ino_cmp (a=0x8898fe90, b=0x898feb0) at rehash.c:173
173	rehash.c: No such file or directory.
 	in rehash.c

The full backtrace: http://nerdbynature.de/bits/e2fsprogs.pu/e2fsck-1.40.7-Dfv.log

The filesystem in question has been created in 11/2007 - maybe I missed 
some on-disk changes since then and have to recreate the fs?

Thanks,
Christian.
-- 
BOFH excuse #86:

Runt packets

             reply	other threads:[~2008-03-13 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 20:23 Christian Kujau [this message]
2008-03-13 20:49 ` e2fsck -D segfaults in pass 3A Theodore Tso
2008-03-13 21:24   ` Christian Kujau

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=alpine.DEB.1.00.0803132116430.7433@sheep.housecafe.de \
    --to=lists@nerdbynature.de \
    --cc=linux-ext4@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