* e2fsck running extremely slowly
@ 2013-07-21 22:45 H. Peter Anvin
2013-07-22 1:29 ` Theodore Ts'o
0 siblings, 1 reply; 3+ messages in thread
From: H. Peter Anvin @ 2013-07-21 22:45 UTC (permalink / raw)
To: linux-ext4
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: e2fsck running extremely slowly
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
0 siblings, 1 reply; 3+ messages in thread
From: Theodore Ts'o @ 2013-07-22 1:29 UTC (permalink / raw)
To: H. Peter Anvin; +Cc: linux-ext4
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.
- Ted
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: e2fsck running extremely slowly
2013-07-22 1:29 ` Theodore Ts'o
@ 2013-07-22 2:35 ` H. Peter Anvin
0 siblings, 0 replies; 3+ messages in thread
From: H. Peter Anvin @ 2013-07-22 2:35 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: linux-ext4
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-07-22 2:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).