Date: Fri, 22 Oct 2004 19:09:50 -0400 (EDT) From: Mikhail Teterin <mi@aldan.algebra.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo Message-ID: <200410222309.i9MN9oqo000754@250-217.customer.cloud9.net> Resent-Message-ID: <200410222310.i9MNAUZ4004171@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 73019 >Category: bin >Synopsis: fsck_ufs: cannot alloc 607016868 bytes for inoinfo >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >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: >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: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410222309.i9MN9oqo000754>