From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Akos Csete <akos.csete@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4
Date: Wed, 15 Apr 2015 12:06:14 -0700 [thread overview]
Message-ID: <20150415190614.GA11592@birch.djwong.org> (raw)
In-Reply-To: <CAD-ux60opdAx0+t3EmwR1GWT6t3rZv7CXhxNNbwQLKX6jz_z7Q@mail.gmail.com>
On Wed, Apr 15, 2015 at 11:18:18AM -0400, Akos Csete wrote:
> I ran into a very long execution time, approaching 48 hours, with
> e2fsck 1.42.9 when running e2fsck -fyv on a 7.8TB volume after
> fsck.ext4 -nf found 1761 inodes containing multiply-claimed blocks.
> I've been tailing the e2fsck output combined with a timestamp and
> found progress is extremely slow.
> Is this slow processing expected? I checked Ted's response to a 2009
> posting for ext3 with a similar issue where he recommended selectively
> wiping inodes with debugfs clri then restoring files as needed. Are
> there any other options for ext4, perhaps other/faster repair
> alternatives?
Unfortunately, the multiple-blocks cleaner runs one block at a time and is
quite slow. 1.42.12 might improve things somewhat since I cleaned out some of
the stranger things it would do, but it's still not fast.
(Some day in the future maybe we'll support reflink in which case this whole
part of fsck can go away.)
--D
>
> Thanks,
> Akos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-15 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:18 Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4 Akos Csete
2015-04-15 19:06 ` Darrick J. Wong [this message]
2015-04-16 15:00 ` Theodore Ts'o
2015-04-17 20:05 ` Akos Csete
2015-04-17 21:08 ` Theodore Ts'o
2015-04-18 15:02 ` Andreas Dilger
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=20150415190614.GA11592@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=akos.csete@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).