Date: Sun, 10 Nov 1996 14:30:10 +0000 () From: Brian Tao <taob@io.org> To: FREEBSD-ISP-L <freebsd-isp@FreeBSD.org> Subject: Re: **ccd, disk striping, and fsck problems** Message-ID: <Pine.BSF.3.95.961110142411.10143A-100000@cabal.io.org> In-Reply-To: <199610151658.LAA26097@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Oct 1996, Joe Greco wrote:
>
> csh -c "unlimit; exec fsck -p"
>
> as a way to circumvent the per process memory limit that you may be
> running into.
FWIW, this is what I see when fscking one of my test ccd
filesystems (5x2GB drives). If the amount of memory consumed is
directly proportional to the number of files, then I imagine a large
news spool with several million files might require 40MB or more for
an fsck.
# time fsck -y /dev/rccd0c
** /dev/rccd0c
** Last Mounted on /news/spool
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1207915 files, 10459546 used, 0 free (0 frags, 0 blocks, 0.0% fragmentation)
20.430u 6.885s 16:22.79 2.7% 206+18844k 2+1io 7pf+0w
# df -i
Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
/dev/ccd0c 10459546 10459546 -836763 109% 1207915 1318803 48% /news/spool
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Senior Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961110142411.10143A-100000>
