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 1Od3fN-00069Q-2v for garchives@archives.gentoo.org; Sun, 25 Jul 2010 16:03:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6BAB7E08D4 for ; Sun, 25 Jul 2010 16:03:04 +0000 (UTC) Received: from wlym.com (wlym.com [66.135.63.43]) by pigeon.gentoo.org (Postfix) with ESMTP id 3723EE08E5 for ; Sun, 25 Jul 2010 15:24:53 +0000 (UTC) Received: from ccs.covici.com (pool-71-171-112-166.clppva.fios.verizon.net [71.171.112.166]) (authenticated bits=128) by wlym.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o6PFOoqv004523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 25 Jul 2010 10:24:52 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.4/8.14.4) with ESMTP id o6PFOkVg012873 for ; Sun, 25 Jul 2010 11:24:49 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck In-reply-to: <4C4BF359.4020404@gmail.com> References: <4C4B45B2.4000508@konstantinhansen.de> <201007242221.12550.alan.mckinnon@gmail.com> <4C4BC447.6010803@konstantinhansen.de> <201007250949.17739.alan.mckinnon@gmail.com> <4C4BF359.4020404@gmail.com> Comments: In-reply-to Dale message dated "Sun, 25 Jul 2010 03:18:33 -0500." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.2.1 Date: Sun, 25 Jul 2010 11:24:46 -0400 Message-ID: <12872.1280071486@ccs.covici.com> From: covici@ccs.covici.com 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 X-Archives-Salt: a12cebad-b57f-4092-8d21-82657f0d9023 X-Archives-Hash: 046b4172901a47f17e84aaa2a04a19dc Dale wrote: > Alan McKinnon wrote: > > On Sunday 25 July 2010 06:57:43 KH wrote: > > > >>> You said you ran e2fsck and it was OK. What was the command? > >>> > >>> > >>> > >>> Normally with an e2fsck on a journalled fs, the app will replay the > >>> journal and make a few minor checks. This takes about 4 seconds, not > >>> the 40 minutes it takes to do a ful ext2 check. > >>> > >>> > >>> > >>> I think you might need to fsck without the journal. I know there's a way > >>> to do this but a cursory glance at the man page didn't reveal it. Maybe > >>> an ext user will chip in with the correct method > >>> > >>> > >>> > >>> > >>> > >> Hi, > >> > >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > >> /dev/sde3 . Yes, it only took some seconds. > >> > > It's been a long time since I used ext3 so some of this might be wrong. > > > > An fsck that takes a few seconds is using the journal, which might not uncover > > deeper corruption. You should try disabling the journal (I couldn't find the > > way to do that though), but this will also work: > > > > Boot of a LiveCD, mount your root partition somewhere using type "ext2" and > > fsck it. This will invalidate the journal but that's OK, it gets recreated on > > the next proper boot. Let the fsck finish - it will take a while on a large > > fs. > > > > When done, reboot as normal and see if the machine boots up properly. > > > > > > > > And I would stand guard to make sure housekeeping doesn't come around. > ;-) Cutting power during all this wold not be good. You don't need to invalidate the journal or mount ext2, just use -f if memory serves, be sure the partition is unmounted and that will force a full check. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com