Date: Thu, 28 Apr 2005 21:21:11 +0200 (CEST) From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: fsck_ufs: cannot increase directory list Message-ID: <200504281921.j3SJLBw5033588@lurza.secnetix.de> In-Reply-To: <42711DDE.4060209@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson <anderson@centtech.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504281921.j3SJLBw5033588>