From: Bas van Schaik <bas@tuxes.nl>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck dies with error "this should never happen!!!"
Date: Fri, 22 Feb 2008 14:14:40 +0100 [thread overview]
Message-ID: <47BECAC0.5010707@tuxes.nl> (raw)
In-Reply-To: <20080222123852.GI20118@mit.edu>
Theodore Tso wrote:
> On Fri, Feb 22, 2008 at 01:07:13PM +0100, Bas van Schaik wrote:
>
>> Hi all,
>>
>> Currently, I have a big problem: e2fsck refuses to fix my currupted
>> filesystem...
>>
>
> The things that I would suggest first of all is upgrading to the
> latest version of e2fsprogs. If that doesn't fix it, I'm going to
> need either a compressed e2image file (see the e2image man page) or
> login access to see what is up.
Thanks for the suggestion, I was naively assuming that e2fsck wasn't
under active development. I've installed the statically linked 1.40.6
from Debian Lenny and it's running. However, it will take quite a long
time before it will actually hit the point where the old version found
problems.
I'll let you know what the results are!
Regards,
-- Bas
next prev parent reply other threads:[~2008-02-22 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 12:07 e2fsck dies with error "this should never happen!!!" Bas van Schaik
2008-02-22 12:38 ` Theodore Tso
2008-02-22 13:14 ` Bas van Schaik [this message]
2008-02-22 17:44 ` Bas van Schaik
2008-02-22 17:46 ` Eric Sandeen
2008-02-22 17:55 ` Bas van Schaik
2008-02-22 18:00 ` Eric Sandeen
2008-02-22 18:06 ` Bas van Schaik
2008-02-22 18:27 ` Theodore Tso
2008-02-22 19:31 ` Bas van Schaik
2008-02-22 19:48 ` Theodore Tso
2008-03-02 19:08 ` Bas van Schaik
2008-03-07 13:41 ` Bas van Schaik
2008-03-07 15:50 ` Eric Sandeen
2008-03-07 16:29 ` Bas van Schaik
2008-03-07 17:45 ` Theodore Tso
2008-03-07 18:12 ` Bas van Schaik
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=47BECAC0.5010707@tuxes.nl \
--to=bas@tuxes.nl \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@MIT.EDU \
/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.