From owner-freebsd-questions@FreeBSD.ORG Sun Jul 26 07:56:51 2009 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40E33106566C for ; Sun, 26 Jul 2009 07:56:51 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by mx1.freebsd.org (Postfix) with ESMTP id C16548FC08 for ; Sun, 26 Jul 2009 07:56:50 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: by bwz19 with SMTP id 19so2042573bwz.43 for ; Sun, 26 Jul 2009 00:56:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=G7QnCI0TjA5k5IqKGShk+fNo1XMVxinzB40icsYGsYQ=; b=cNRw50uVeubhl+1eP1t4rwMwTwmvlZfZcbuKctFCT4+plEM92jm1HdsmpRN5K9NN6F 24HMBssQ48lHCPVs1hh779cbh+e4hIU+sRL77OpNGu2oXyT7LjYoxlX7cRaJoF3c0dIm VivzsxeIQmN/gR3nWo04jJ1rXbHJ6d78ay2EU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=eRdhyc6G845cTh3+ArjvFZtH0RuKQ2I0/LCiVQUXKrZ5Amgv7/7UOYup4t0yNk2B9W aK1f9o2YN5FytAFPLXpox/Kkd9ovv1lg0iqrGGJJMWJN4WTc/G+NAov8jIw1wTjTR7ea 5kwmv9gX1S8Hdwu6YoyTQn11hoXYmpmxl/g48= MIME-Version: 1.0 Received: by 10.239.137.194 with SMTP id m2mr577580hbm.119.1248595009737; Sun, 26 Jul 2009 00:56:49 -0700 (PDT) Date: Sun, 26 Jul 2009 07:56:49 +0000 Message-ID: From: "b. f." To: freebsd-questions@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: mkhitrov@gmail.com Subject: Re: UFS2 tuning for heterogeneous 4TB file system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2009 07:56:51 -0000 >The file system in question will not have a common file size (which is >what, as I understand, bytes per inode should be tuned for). There >will be many small files (< 10 KB) and many large ones (> 500 MB). A >similar, in terms of content, 2TB ntfs file system on another server >has an average file size of about 26 MB with 59,246 files. Ordinarily, it may have a large variation in file sizes, but can you intervene, and segregate large and small files in separate filesystems, so that you can optimize the settings for each independently? >Ideally, I would prefer that small files do not waste more than 4 KB >of space, which is what you have with ntfs. At the same time, having >fsck running for days after an unclean shutdown is also not a good >option (I always disable background checking). From what I've gathered >so far, the two requirements are at the opposite ends in terms of file >system optimization. I gather you are trying to be conservative, but have you considered using gjournal(8)? At least for the filesystems with many small files? In that way, you could safely avoid the need for most if not all use of fsck(8), and, as an adjunct benefit, you would be able to operate on the small files more quickly: http://lists.freebsd.org/pipermail/freebsd-current/2006-June/064043.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/article.html gjournal has a lower overhead than ZFS, and has proven to be fairly reliable. Also, you can always unhook it and revert to plain UFS mounts easily. b.