From owner-freebsd-current@FreeBSD.ORG Mon Dec 13 15:15:04 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 AEE2816A4CE for ; Mon, 13 Dec 2004 15:15:04 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C2F043D39 for ; Mon, 13 Dec 2004 15:15:03 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id iBDFExk7071999 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 13 Dec 2004 16:14:59 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id iBDFExlv071998 for freebsd-current@freebsd.org; Mon, 13 Dec 2004 16:14:59 +0100 (CET) Date: Mon, 13 Dec 2004 16:14:59 +0100 From: Divacky Roman To: freebsd-current@freebsd.org Message-ID: <20041213151459.GA70441@stud.fit.vutbr.cz> References: <20041212090656.GA98988@stud.fit.vutbr.cz> <200412121135.43408.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412121135.43408.michaelnottebrock@gmx.net> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: Re: strange df output 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, 13 Dec 2004 15:15:04 -0000 in fact, nothing was broken (except the free space number)... On Sun, Dec 12, 2004 at 11:35:38AM +0100, Michael Nottebrock wrote: > On Sunday, 12. December 2004 10:06, Divacky Roman wrote: > > Hi, > > > > with recent 6-current I had to reboot my machine (I tried mount my cdrom > > but the process hanged in kernel then everything started to crash). > > > > after panic, fsck was invoken: > > witten ~# fsck / > > ** /dev/ad0s1a (NO WRITE) > > ** Last Mounted on / > > ** Root file system > > ** Phase 1 - Check Blocks and Sizes > > fsck_ufs: cannot alloc 3221471004 bytes for inoinfo > > > > and df shows this: > > witten ~# df > > Filesystem Size Used Avail Capacity Mounted on > > /dev/ad0s1a 143G 4.5T -4.4T 3520% / > > > > > > is this a known problem? what can I do with it? > > Kinda, see this thread: > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/043670.html > > From all of my experience, you can consider this filesystem busted. Try to get > as much data off it as you can (chances are some files are so corrupt that > you'll get a hang when you try to copy them) and take care to preserve file > modes & permissions, then newfs and restore. > > It's kinda sad, but right now soft-updates must probably be considered unsafe > for some configurations. The reliability in the case of crashes is about just > as bad as mounting something async... my guess is that it's not really a new > bug in softupdates, but rather effects from modern big ata drives with big > caches and write caching enabled (and no tagged queueing - although IIRC the > ata tags support is disabled in 5.x and -CURRENT anyway). > > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org