Date: Mon, 2 Apr 2007 11:13:33 -0500 (CDT) From: dan@more.net To: FreeBSD-gnats-submit@FreeBSD.org Cc: dan@more.net Subject: bin/111146: fsck fails on 6T filesystem Message-ID: <20070402161333.75A4D5C3C@wallenda.spg.more.net> Resent-Message-ID: <200704021650.l32Go1ma079720@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 111146
>Category: bin
>Synopsis: fsck fails on 6T filesystem
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Apr 02 16:50:00 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: Dan D Niles
>Release: FreeBSD 6.2-RELEASE-p3 i386
>Organization:
MOREnet - Missouri Research and Education Network
>Environment:
System: FreeBSD hostname 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #5: Wed Mar 28 07:44:39 CDT 2007 root@hostname:/usr/obj/usr/src/sys/BIG_MEM i386
>Description:
I have a 6T filesystem on a server that crashed. I cannot fsck
the filesystem.
# fsck -t ufs -y /dev/da0
fsck_ufs: cannot alloc 1993797728 bytes for inoinfo
I also tried:
# fsck -t ufs -f -p /dev/da0
/dev/da0: UNKNOWN FILE TYPE I=11895232
/dev/da0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I built a custom kernel with MAXDSIZ and DFLDSIZ just under 3G, and got
the same results. It was at about 430M in use when it crashed, so the
total would be 2332 M which is less that the size allowed (reported by
limits).
NOTE: I have temporarily replaced the server. For a short time I have the
crashed filesystem available for testing and debugging code. I have
a core dump from the fsck.
>How-To-Repeat:
On a 6T filesystem that has crashed, run:
fsck -t ufs -y /dev/da0
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070402161333.75A4D5C3C>