From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 19:21:13 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C99DB16A4CE for ; Thu, 28 Apr 2005 19:21:13 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE4A443D2D for ; Thu, 28 Apr 2005 19:21:12 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (netwva@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j3SJLB5d033589 for ; Thu, 28 Apr 2005 21:21:11 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j3SJLBw5033588; Thu, 28 Apr 2005 21:21:11 +0200 (CEST) (envelope-from olli) Date: Thu, 28 Apr 2005 21:21:11 +0200 (CEST) Message-Id: <200504281921.j3SJLBw5033588@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <42711DDE.4060209@centtech.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: fsck_ufs: cannot increase directory list X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2005 19:21:13 -0000 Eric Anderson wrote: > I rebooted my server, and fsck'ed the disks, and here's what I get: > > # fsck -y /vol1 > ** /dev/da0s1d > ** Last Mounted on /vol1 > ** Phase 1 - Check Blocks and Sizes > fsck_ufs: cannot increase directory list That error message is printed if a memory allocation fails. (It's the memory that fsck uses for caching the inodes of directories.) > # df -i > Filesystem 1K-blocks Used Avail Capacity iused > ifree %iused Mounted on > /dev/da0s1d 1891668564 1643042028 97293052 94% 32927755 > 211542003 13% /vol1 > > What's wrong? It lets me mount it rw and ro, but I'm afraid data is > going to get corrupt. Well, you have a 2 Tbyte filesystem with nearly 250 million inodes. That's really a lot, and fsck will need a lot of memory (and probably run for a long time). First you should check if you hit a (soft or hard) resource limit with the "ulimit" command. See sh(1) for details on the ulimit usage. If you ran fsck in single user mode, you might have to enable swapping beforehand ("swapon -a") if your physical RAM is not sufficient. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I suggested holding a "Python Object Oriented Programming Seminar", but the acronym was unpopular. -- Joseph Strout