From root@250-217.customer.cloud9.net  Fri Oct 22 23:10:02 2004
Return-Path: <root@250-217.customer.cloud9.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CED8A16A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 22 Oct 2004 23:10:02 +0000 (GMT)
Received: from corbulon.video-collage.com (aldan.algebra.com [216.254.65.224])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5367243D64
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 22 Oct 2004 23:10:02 +0000 (GMT)
	(envelope-from root@250-217.customer.cloud9.net)
Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])
	by corbulon.video-collage.com (8.12.11/8.12.11) with ESMTP id i9MN9wKF047243
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 22 Oct 2004 19:09:58 -0400 (EDT)
	(envelope-from root@250-217.customer.cloud9.net)
Received: from 250-217.customer.cloud9.net (smmsp@localhost [127.0.0.1])
	by 250-217.customer.cloud9.net (8.13.1/8.13.1) with ESMTP id i9MN9pJr000755
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 22 Oct 2004 19:09:51 -0400 (EDT)
	(envelope-from root@250-217.customer.cloud9.net)
Received: (from root@localhost)
	by 250-217.customer.cloud9.net (8.13.1/8.13.1/Submit) id i9MN9oqo000754;
	Fri, 22 Oct 2004 19:09:50 -0400 (EDT)
	(envelope-from root)
Message-Id: <200410222309.i9MN9oqo000754@250-217.customer.cloud9.net>
Date: Fri, 22 Oct 2004 19:09:50 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
To: FreeBSD-gnats-submit@freebsd.org
Subject: fsck_ufs: cannot alloc 607016868 bytes for inoinfo
X-Send-Pr-Version: 3.113

>Number:         73019
>Category:       bin
>Synopsis:       [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for inoinfo
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-fs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 22 23:10:30 GMT 2004
>Closed-Date:    
>Last-Modified:  Mon May 18 03:04:29 UTC 2009
>Originator:     Mikhail Teterin
>Release:        FreeBSD 6.0-CURRENT i386
>Organization:
Virtual Estates, Inc.
>Environment:
System: FreeBSD mi.us.murex.com 6.0-CURRENT FreeBSD 6.0-CURRENT #2: Fri Oct 22 15:20:29 EDT 2004 root@mi.us.murex.com:/meow/obj/misha/src/sys/Gigabyte i386

>Description:
	After certain amount of panics and hangs, I have -- for the second
	time -- a filesystem, which defeats fsck:

		** /dev/ad4e
		** Last Mounted on /misha
		** Phase 1 - Check Blocks and Sizes
		fsck_ufs: cannot alloc 607016868 bytes for inoinfo

>How-To-Repeat:
	Not sure.

>Fix:

	The first time this happened, I just re-newfsed the partition.
	This time it is on a bigger one, with valuable data. The FS can
	be mounted read-only, I'm going to try to back up, what I can and
	recreate it.
>Release-Note:
>Audit-Trail:

From: Mikhail Teterin <mi+kde@aldan.algebra.com>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo
Date: Sat, 23 Oct 2004 00:36:26 -0400

 As I the tar finished and I tried to unmount the troublesome
 filesystem (mounted readonly) to reformat it, the OS paniced with
 
  Consumer with zero access count in g_dev_strategy
 
 When I typed `call boot(0)' in the debugger, there were 3439 buffers
 remaining. The system gave on 85 buffers.
 
  -mi
 

From: "Brett E. Wynkoop" <wynkoop@wynn.com>
To: freebsd-gnats-submit@FreeBSD.org, mi@aldan.algebra.com
Cc:  
Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo
Date: Sun, 12 Dec 2004 02:22:09 -0500

 Greeting-
      I just had the exact same problem in FreeBSD 5.3.  In my case it is 
 my var partition on a just installed system.  It will not FSCK using any
 superblock and I can not even mount the FS read only. 
      I had softupdates off for the file system.  Before the failure
 happened
 I was getting DMA write failure errors on the console for the ad0.
 
 -Brett

From: Mikhail Teterin <mi@corbulon.video-collage.com>
To: wynkoop@wynn.com
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo
Date: Sun, 12 Dec 2004 16:17:23 -0500 (EST)

 > Greeting-
 >      I just had the exact same problem in FreeBSD 5.3.  In my case it is 
 > my var partition on a just installed system.  It will not FSCK using any
 > superblock and I can not even mount the FS read only. 
 >      I had softupdates off for the file system.  Before the failure
 > happened
 > I was getting DMA write failure errors on the console for the ad0.
 
 Are you using Silicon Image's SATA controller by any chance? See
 
 	http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72451
 
 As for recovering your /var, there are, apparently, a lot more superblock
 copies, than fsck tries automatically.
 
 To get the actual number, try newfs-ing the partition with exactly the
 same parameters as before, but with ``-N'' flag. This will print out the
 addresses of the superblocks. See if giving one of them to fsck_ufs with
 ``-b'' will help you recover stuff. I have not tried this personally, but
 it seems like you've lost your /var anyway...
 
 	-mi

From: wynkoop@wynn.com
To: mi@corbulon.video-collage.com (Mikhail Teterin)
Cc: wynkoop@wynn.com, freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo
Date: Sun, 12 Dec 2004 21:36:35 +0000 (GMT)

 > 
 > > Greeting-
 > >      I just had the exact same problem in FreeBSD 5.3.  In my case it is 
 > > my var partition on a just installed system.  It will not FSCK using any
 > > superblock and I can not even mount the FS read only. 
 > >      I had softupdates off for the file system.  Before the failure
 > > happened
 > > I was getting DMA write failure errors on the console for the ad0.
 > 
 > Are you using Silicon Image's SATA controller by any chance? See
 > 
 > 	http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72451
 > 
 > As for recovering your /var, there are, apparently, a lot more superblock
 > copies, than fsck tries automatically.
 > 
 > To get the actual number, try newfs-ing the partition with exactly the
 > same parameters as before, but with ``-N'' flag. This will print out the
 > addresses of the superblocks. See if giving one of them to fsck_ufs with
 > ``-b'' will help you recover stuff. I have not tried this personally, but
 > it seems like you've lost your /var anyway...
 > 
 > 	-mi
 > 
 
 Greeting-
      I tried about 15 alternate superblocks to no good end.  Also there is
 a bug in fsck(8) where it claims that the first alternate superblock is at
 32, and that is where it tells fsck_ufs(8) to look, but at least on my
 5.3 system the first alternate superblock is at 160.  
      There is also another bug in fsck(8) in that it will not pass the 
 -b SUPERBLOCKNUM on to fsck_ufs, instead it returns an error stating that
 -b is an illegal option.  Talk about a way to confuse someone that is new
 to BSD!  Glad I have 20 years working on BSD systems!
 
      I have reinstalled from CD rom and am in the process of reinstalling
 the needed ports.  No user data was lost as I preserved that partition, but
 this problem makes me a little shy to bring the 5.3 system on line.  It was
 to replace a solaris 2.4 running on a 486dx66, but for now the solaris 
 will have to stay.
 
      The raid controler is an IDE unit that requires no special software.
 To the system it looks just like an IDE disk, and you connect 2 same size
 IDE disks to the control unit.  The one I am using in the 5.3 system is an
 older unit called the ARaid99-300.  If you were to want to get one
 today I would instead suggest the units that are made by ARCO in florida.
 They can be found at http://www.arcoide.com/.  I have several of those
 units doing a fine job at various sites.
      BTW the systems shows the raid controler as this:
 
 ad0: 38166MB <ASI ARAID99/Rev1.14> [77545/16/63] at ata0-master UDMA33
 
 at boot time.
 
 -Brett
 
 -- 
 DRM is theft!  We are the stakeholders!  http://www.nyfairuse.org/
 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Sat Nov 12 17:29:06 GMT 2005 
State-Changed-Why:  
Is this still a problem in 6.0-RELEASE? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73019 
State-Changed-From-To: feedback->open 
State-Changed-By: linimon 
State-Changed-When: Sat Nov 12 22:26:57 GMT 2005 
State-Changed-Why:  
Feedback received, although feedback from the submitter is still requested. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73019 
Responsible-Changed-From-To: freebsd-bugs->freebsd-fs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon May 18 03:04:18 UTC 2009 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73019 
>Unformatted:
