From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PwI8r-0003B7-JX for garchives@archives.gentoo.org; Sun, 06 Mar 2011 17:53:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 611521C063; Sun, 6 Mar 2011 17:51:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 318DF1C063 for ; Sun, 6 Mar 2011 17:51:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id B5C921B4039 for ; Sun, 6 Mar 2011 17:51:01 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Score: -2.866 X-Spam-Level: X-Spam-Status: No, score=-2.866 required=5.5 tests=[AWL=-0.267, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjkjMNepidRC for ; Sun, 6 Mar 2011 17:50:55 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id 235541B4067 for ; Sun, 6 Mar 2011 17:50:52 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PwI6T-0007bt-J6 for gentoo-user@gentoo.org; Sun, 06 Mar 2011 18:50:49 +0100 Received: from athedsl-377831.home.otenet.gr ([79.131.27.229]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Mar 2011 18:50:49 +0100 Received: from realnc by athedsl-377831.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Mar 2011 18:50:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: How do I show list of bad blocks on a disk? Date: Sun, 06 Mar 2011 19:51:11 +0200 Organization: Lucas Barks Message-ID: References: <4D73C384.5040100@wonkology.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: athedsl-377831.home.otenet.gr User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110306 Thunderbird/3.1.9 In-Reply-To: <4D73C384.5040100@wonkology.org> X-Archives-Salt: X-Archives-Hash: 25fa6ccaec70a2deed9f295e0da376c8 On 03/06/2011 07:25 PM, Alex Schuster wrote: > Nikos Chantziaras writes: > >> Before leaving home, I started an fsck.ext4 on a filesystem (500GB) that >> resides on a disk that I suspect is damaged: >> >> fsck.ext4 -c -c -f /dev/sdb1 >> >> When I came back 10 hours later, it was still checking. After 2 hours >> more (so it took 12 hours total) it finally finished. The output was > > Anything about erros in dmesg or syslog? Nope. All clean. >> [...] >> Were there any bad blocks or not? Is >> there a way to query the filesystem for the now known bad blocks? (The >> "Updating bad block inode." message suggests that such a list is stored >> directly inside the filesystem.) > > dumpe2fs -b /dev/sdb1 probably also works for ext4. Thanks. I just tried and it prints nothing. I guess that means no bad blocks were found. (Rant: Don't you just love programs that instead of explicitly telling you that all is OK, they just stay silent, leaving you wondering whether they actually work at all? Argh...)