linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-ext4@vger.kernel.org
Subject: e2fsck running extremely slowly
Date: Sun, 21 Jul 2013 15:45:20 -0700	[thread overview]
Message-ID: <51EC6480.6000200@zytor.com> (raw)

I have a large filesystem (14 TB) which suffered a RAID failure which
seems to have corrupted some inodes.  Unfortunately as a result there
are now a number of inodes with "false extents" which result in a very
large number of multiply claimed blocks.

I have tried to run e2fsck on this filesystem, and it gets as far as
phase 1D, at which point it starts running at a glacial pace.  After 48
hours -- most of it sitting at 100% CPU executing no system calls at all
-- it claims to have processed a single file out of almost 10000.

Anything I can do (to rescue the filesystem or try to debug the problem)
other than "wipe and start over"?

I believe this is e2fsck 1.42.3 from Fedora 17.

	-hpa

             reply	other threads:[~2013-07-21 22:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 22:45 H. Peter Anvin [this message]
2013-07-22  1:29 ` e2fsck running extremely slowly Theodore Ts'o
2013-07-22  2:35   ` H. Peter Anvin

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=51EC6480.6000200@zytor.com \
    --to=hpa@zytor.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).