From: Theodore Ts'o <tytso@mit.edu>
To: "kaefert@gmail.com" <kaefert@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck extremly slow after: EXT4-fs.. ext4_check_descriptors: Checksum for group .. failed
Date: Mon, 12 Nov 2012 11:16:46 -0500 [thread overview]
Message-ID: <20121112161646.GF4895@thunk.org> (raw)
In-Reply-To: <CACDumsTj9S2eLNG+zNFY_9ZCZdKGDVVz5SF2BqapS3JvvYP8AA@mail.gmail.com>
On Sun, Nov 11, 2012 at 07:14:40PM +0100, kaefert@gmail.com wrote:
>
> So it took several days, but after running it manually it finished to
> run after a few days. However, It doesn't seem to get the filesystem
> in a truely clean state, although it doesn't print an error (at least
> not at the end), because I've ran e2fsck again on the same partition
> and it found errors again. Here's the output of the last run that
> completed:
You said this is an external USB drive, right? How big is it? If
it's affordable, something I would suggest doing is to make image copy
(i.e., using dd or dd_rescue) to another external USB drive, just to
rule out hardware issues.
The Pass 1B/1C/1D errors, particularly if you are seeing the exact
same pattern after running a full e2fsck -fy run, makes me suspicious
that inode table blocks are getting written to the wrong location on
disk --- and whether this is caused by the storage device failing in
some strange way.
Also, can you save the output of e2fsck to a file? Direct the output
to a log file, so I can look at it. There are patterns of the
"millions of entries of the same pattern" which you've elided which
can be a hint. Also, can you disable the German translation to make
it easier for me to investigate?
Thanks,
- Ted
next prev parent reply other threads:[~2012-11-12 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 8:23 e2fsck extremly slow after: EXT4-fs.. ext4_check_descriptors: Checksum for group .. failed kaefert
2012-11-09 0:01 ` Theodore Ts'o
2012-11-09 6:05 ` kaefert
2012-11-11 18:14 ` kaefert
2012-11-12 16:16 ` Theodore Ts'o [this message]
2012-11-12 16:29 ` kaefert
2012-11-13 21:09 ` Andreas Dilger
2012-11-13 21:24 ` Theodore Ts'o
2012-11-15 11:51 ` kaefert
2012-11-16 18:14 ` Theodore Ts'o
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=20121112161646.GF4895@thunk.org \
--to=tytso@mit.edu \
--cc=kaefert@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).