From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 02:48:46 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 836CD16A4CE for ; Mon, 29 Nov 2004 02:48:46 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 843AA43D54 for ; Mon, 29 Nov 2004 02:48:45 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 21129 invoked by uid 65534); 29 Nov 2004 02:48:43 -0000 Received: from pD95D8F14.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.20) by mail.gmx.net (mp002) with SMTP; 29 Nov 2004 03:48:43 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAT2mXMo010663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Nov 2004 03:48:36 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41AA8E00.2050401@gmx.net> Date: Mon, 29 Nov 2004 03:48:32 +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: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: 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 02:48:46 -0000 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. Is there really no way that fsck could be made smarter about dealing with seemingly huge filesystems? Also, what kind of memory would be required to fsck a _real_ 11TB filesystem? -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org