linux-ext4 - Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAD-ux60opdAx0+t3EmwR1GWT6t3rZv7CXhxNNbwQLKX6jz_z7Q@mail.gmail.com>
Date:	Wed, 15 Apr 2015 11:18:18 -0400
From:	Akos Csete <akos.csete@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Fsck repair takes very long for 1,761 inodes containing
 multiply-claimed blocks on ext4

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?

Thanks,
Akos
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html