linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kaefert@gmail.com" <kaefert@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck extremly slow after: EXT4-fs.. ext4_check_descriptors: Checksum for group .. failed
Date: Fri, 9 Nov 2012 07:05:02 +0100	[thread overview]
Message-ID: <CACDumsRP6+AMZdCPgyH03_NBrCWY8m_1Gp2DD9aMwqh9DtpEhA@mail.gmail.com> (raw)
In-Reply-To: <20121109000156.GQ19977@thunk.org>

2012/11/9 Theodore Ts'o <tytso@mit.edu>
>
> 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

Hi there Ted!

Thanks for the answer! Of course I understand that when you want to
debug something you really gotta run it from the console, It's just
when I started to run this, I did not think anything would go wrong,
you never think it hits you ;)

After e2fsck failed for the first time (where I don't know why, since
gparted crashed after I tried to save the details), I started to run
e2fsck manually, and since the -p option made him cancel the run I
started a third run in interactive mode. I've posted the console
output of this second and third run as an update to my question at
serverfault.com (see
http://serverfault.com/questions/446074/e2fsck-extremely-slow-although-enough-memory-exists
- start reading at "UPDATE4")

The 3rd run is still running (since about 20 hours now) and showing
the same pattern as the first run that failed after 78 hours.


Thanks for looking at this,

Thomas K.

  reply	other threads:[~2012-11-09  6:05 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 [this message]
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=CACDumsRP6+AMZdCPgyH03_NBrCWY8m_1Gp2DD9aMwqh9DtpEhA@mail.gmail.com \
    --to=kaefert@gmail.com \
    --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 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).