From owner-freebsd-current@FreeBSD.ORG Mon Dec 8 21:48:00 2003 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 3D18A16A4CE for ; Mon, 8 Dec 2003 21:48:00 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6134343D32 for ; Mon, 8 Dec 2003 21:47:55 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 8197 invoked from network); 9 Dec 2003 05:47:54 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 9 Dec 2003 05:47:54 -0000 Date: Tue, 9 Dec 2003 07:48:41 +0200 From: Ion-Mihai Tetcu To: Doug White Message-Id: <20031209074841.23c16ecb.itetcu@apropo.ro> In-Reply-To: <20031208124541.W15361@carver.gumbysoft.com> References: <20031208181611.1a358bb5.itetcu@apropo.ro> <20031208202837.4a05d06a.itetcu@apropo.ro> <20031208124541.W15361@carver.gumbysoft.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re[2]: (a new fsdb dump) Re: fsck sig 11 (cannot alloc 4216257920bytes for inoinfo) 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: Tue, 09 Dec 2003 05:48:00 -0000 On Mon, 8 Dec 2003 12:47:27 -0800 (PST) Doug White wrote: > On Mon, 8 Dec 2003, Ion-Mihai Tetcu wrote: > > > Here is a fsdb dump on the previous and next inode, hoepe it serves at > > something. THE FOLLOWING DISK SECTORS COULD NOT BE READ means bad > > hardware ? It would be strange as the HDD is 6 month old and smart > > doeasn't report anything. > > The block numbers are impossibly large. It appears you have a fatal level > of disk and filesystem corruption. I'm pretty sure it is fully reproducible. > I would suggest pulling down the > Seagate test tools and running a scan on your disk, then newfs & > reinstall. I've burned a SeaTools image and did all the tests; no problems reported SMART, interal test, surface test - all OK. And now I am really stuck. Any more hints on what to do ? I could newfs the disk again and do a complete install, do something with havy disk IO, hard reset and see if it happends again. But somehow I fear to do that as it will only hide the problem. Either way this shouln't happend (tm) :-/ so could wait a little more time if someone wants to investigate this further. What's the candidate dump/restore, newfs ? -- IOnut Unregistered ;) FreeBSD user