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: Thu, 8 Nov 2012 19:01:56 -0500 [thread overview]
Message-ID: <20121109000156.GQ19977@thunk.org> (raw)
In-Reply-To: <CACDumsQsF4JoqygHT+8wQKz-=zuMPjTccrK1mnHnAZsf36O_Cg@mail.gmail.com>
On Wed, Nov 07, 2012 at 09:23:22AM +0100, kaefert@gmail.com wrote:
> Hi there!
>
> I've got this problem with an ext4 filesystem on an external usb disk
> of mine, I've documented the problem (and my approaches for solving
> it) here:
> http://serverfault.com/questions/446074/e2fsck-extremly-slow-although-enough-memory-exists
>
> I started gparted and with it e2fsck is around 2012-11-04_2200 and its
> 2012-11-07_0923 right now (CET).
> It used up nearly 57 hours of cpu time since then, and I would like to
> find out if and when it will finish.
> Can somebody tell me if and how I could get this information?
Can you please run e2fsck from the command line, and capture the
output (i.e., using "script"). I really need the e2fsck output to
understand what is going on. The strace output is really not helpful.
In general, you may be better off simply not trusting gparted to run
e2fsck and resize2fs for you. If there are no problems I'm sure it's
fine, but it's really hard to debug things if you insist on letting
gparted swallon all of the useful debugging output....
- Ted
next prev parent reply other threads:[~2012-11-09 0:01 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 [this message]
2012-11-09 6:05 ` kaefert
2012-11-11 18:14 ` kaefert
2012-11-12 16:16 ` Theodore Ts'o
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=20121109000156.GQ19977@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).