From: "H. Peter Anvin" <hpa@zytor.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck running extremely slowly
Date: Sun, 21 Jul 2013 19:35:35 -0700 [thread overview]
Message-ID: <51EC9A77.6090109@zytor.com> (raw)
In-Reply-To: <20130722012929.GA30902@thunk.org>
On 07/21/2013 06:29 PM, Theodore Ts'o wrote:
> On Sun, Jul 21, 2013 at 03:45:20PM -0700, H. Peter Anvin wrote:
>> 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.
>
> What I usually do when I is to look at the inodes that are corrupted
> in phases 1b, and examine them using debugfs. If they look insane,
> nuke them using the debugfs clri command.
>
> Yes, this is horribly manual. The long term planned solution is that
> the metadata checksum feature will allow us to determine the metadata
> is corrupt, and then e2fsck will know which fs metadata it can trust,
> and which it will have to discard.
>
Manual isn't really practical with almost 10,000 reported inodes...
-hpa
prev parent reply other threads:[~2013-07-22 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 22:45 e2fsck running extremely slowly H. Peter Anvin
2013-07-22 1:29 ` Theodore Ts'o
2013-07-22 2:35 ` H. Peter Anvin [this message]
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=51EC9A77.6090109@zytor.com \
--to=hpa@zytor.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).