From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Ts'o Subject: Re: Running fsck of huge ext4 partition takes weeks Date: Fri, 28 Aug 2015 13:53:25 -0400 Message-ID: <20150828175325.GB10211@thunk.org> References: <28A25D6A-DA5A-42D2-9BFE-9F6C95B51BE7@dilger.ca> <20150827190548.GC3357@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andreas Dilger , linux-ext4@vger.kernel.org To: Alexander Afonyashin Return-path: Received: from imap.thunk.org ([74.207.234.97]:52868 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752842AbbH1Rx2 (ORCPT ); Fri, 28 Aug 2015 13:53:28 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: If dumpe2fs is hanging as well, it's likely that the problem may be at the hardware level. You might want to check dmesg or the kernel log to see if there are any I/O errors being reported from hard drive. What might be happening is that when a program (such as e2fsck or dumpe2fs) tries to read from a specific part of the hard drive, the hard drive is retrying a large number of times because the hard drive head or platter surface has gotten damaged in some way. It might also be a good idea to check the S.M.A.R.T. status using the smartctl program. Cheers, - Ted