From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 03:31:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A3916A4CF for ; Mon, 29 Nov 2004 03:31:29 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C1C443D48 for ; Mon, 29 Nov 2004 03:31:28 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 14491 invoked by uid 65534); 29 Nov 2004 03:31:27 -0000 Received: from pD95D8F14.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.20) by mail.gmx.net (mp012) with SMTP; 29 Nov 2004 04:31:27 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAT3VMMo011439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Nov 2004 04:31:24 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41AA9808.4050903@gmx.net> Date: Mon, 29 Nov 2004 04:31:20 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Scott Long References: <41AA8E00.2050401@gmx.net> <41AA944A.5090109@freebsd.org> In-Reply-To: <41AA944A.5090109@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-current@freebsd.org Subject: Re: fsck shortcomings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 03:31:29 -0000 Scott Long wrote: > Michael Nottebrock wrote: > >> I recently had a filesystem go bad on me in such a way that it was >> recognized way bigger than it actually was, causing fsck to fail while >> trying to allocate and equally astronomic amount of memory (and my >> machine already had 1 Gig of mem + 2 Gig swap available). >> I just newfs'd and I'm now in the process of restoring data, however, >> I googled a bit on this and it seems that this kind of fs corruption >> is occurring quite often, in particular due to power failures. > > > Yes, very troubling. You said that the alternate superblocks didn't > help? Yes, although that might have been bad luck - I didn't realise something was wrong with the fs right away. Since I had background fsck enabled, the filesystem got mounted anyway, but the system hung at executing dhclient, so I fiddled around with disabling acpi/apic & other stuff, assuming that something was wrong with the NIC or the NIC driver... I guess the alternate superblock might have worked if I had recognized the problem at once and tried fsck_ffs -b right away instead of mounting the bad fs over and over while trying to fix the NIC. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org