From owner-freebsd-fs@FreeBSD.ORG Wed Jan 7 16:26:32 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9774D16A4CE for ; Wed, 7 Jan 2004 16:26:32 -0800 (PST) Received: from beelzebubba.sysabend.org (alcatraz.inna.net [209.201.74.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41A6343D5D for ; Wed, 7 Jan 2004 16:26:30 -0800 (PST) (envelope-from xyzzy@moo.sysabend.org) Received: from moo.sysabend.org (moo.sysabend.org [66.111.41.70]) by beelzebubba.sysabend.org (Postfix) with SMTP id 3CDFF14E99 for ; Wed, 7 Jan 2004 19:26:42 -0500 (EST) Received: (nullmailer pid 76199 invoked by uid 14); Thu, 08 Jan 2004 00:26:27 -0000 Date: Wed, 7 Jan 2004 16:26:27 -0800 From: Tom Arnold To: freebsd-fs@freebsd.org Message-ID: <20040108002627.GH22041@moo.sysabend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Organization: The Sysabend Dump X-Operating-System: CPM2.2 X-8-Bit-Samples-And-Analog-Filters: Rah! X-Bucket-Brigade-Devices: Rah! Subject: Large filesystems with massive inodes on BSD5.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: xyzzy@sysabend.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 00:26:32 -0000 Greetings I'm building a fileserver thats going to house a large number of small files ( no, not an innd server but same idea sorta ). I've got a 3.3TB RAID hanging off a FreeBSD 5.2-RC box ( cvsup'd to RELENG_5_2 monday night ). I've broken it up into 2 1TB filesystems newfs'd "stock" and the remainder a 1TB partition and a 300gig partition. Now the fun part. newfs'd the final two partitions -b 4096 -f 512 -i 512 as they are going to have many many small files on them. Needless to say if the server reboots unexpectedly fsck takes a long long to run. So this is why for a production server I'm playing with 5.2 Newfs'd UFS2 softupdates enabled. Crash the box to force a dirty reboot. Boots finally after about 20 minutes of playing with snapshots. About 4 hours later I get this lovely error : Jan 7 02:58:12 tarnold2 fsck: /dev/da1s1e: CANNOT CREATE SNAPSHOT /export/database/.snap/fsck_snapshot: File too large Jan 7 02:58:12 tarnold2 fsck: Jan 7 02:58:12 tarnold2 fsck: /dev/da1s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Jan 7 20:21:24 tarnold2 su: tarnold to root on /dev/ttyp0 da1s1e is the largest or the two filesystems with huge numbers of inodes. Am I running into some kind of filesystem limits by having 2billion inodes on it? Am I even asking on the correct mailing list or should I ask this on -Current? Thanks. -- ------------------------------------------------------------------------ - Tom Arnold - When I was small, I was in love, - - Sysabend - In love with everything. - - CareTaker - And now there's only you... - -------------- -- Thomas Dolby, "Cloudburst At Shingle Street" -