From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21805 invoked by alias); 8 Apr 2004 22:31:49 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 21790 invoked from network); 8 Apr 2004 22:31:48 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 8 Apr 2004 22:31:48 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i38MVmMC015408 for ; Thu, 8 Apr 2004 18:31:48 -0400 Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [172.16.52.154]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i38MVmj01517; Thu, 8 Apr 2004 18:31:48 -0400 Received: from localhost (mgalgoci@localhost) by lacrosse.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i38MVm827748; Thu, 8 Apr 2004 18:31:48 -0400 X-Authentication-Warning: lacrosse.corp.redhat.com: mgalgoci owned process doing -bs Date: Thu, 08 Apr 2004 22:31:00 -0000 From: Matthew Galgoci X-X-Sender: mgalgoci@lacrosse.corp.redhat.com To: law@redhat.com cc: Christopher Faylor , David Edelsohn , Subject: Re: A time to pause and fsck In-Reply-To: <200404082050.i38KoEPD025949@speedy.slc.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-q2/txt/msg00142.txt.bz2 > >I'm happy to fsck it right now if I have the go-ahead. > That's fine by me. > > I'd suggest that if there aren't any objections within the next 30 minutes > that you go ahead with the fsck. Again, I'd rather be safe than sorry given > the problems we're having. Ok, this is done. Apparently forcefsck doesn't seem to work for logical volumes. I had to drop the machine to single user mode, unmount everything a lv at a time, and fsck by hand. cvs-temp was indeed dirty, requiring multiple passes of e2fsck. Any inodes that were orphaned were connected to lost+found. /home also had a few deleted inodes that needed to be cleared. Recommendation: after each crash, the system needs to be fscked by hand. -- Matthew Galgoci System Administrator and Sr. Manager of Ruminants Red Hat, Inc 919.754.3700 x44155