From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 11:57:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8353616A41F; Wed, 20 Jul 2005 11:57:26 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E4C543D45; Wed, 20 Jul 2005 11:57:25 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j6KBvL43054377; Wed, 20 Jul 2005 06:57:25 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42DE3C1F.9070704@centtech.com> Date: Wed, 20 Jul 2005 06:57:19 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Thomas E. Zander" References: <42DD64AB.3000605@centtech.com> <20050720094830.GR782@marvin.riggiland.au> In-Reply-To: <20050720094830.GR782@marvin.riggiland.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/984/Tue Jul 19 04:16:09 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: mksnap_ffs takes 4-5 minutes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2005 11:57:26 -0000 Thomas E. Zander wrote: > Hi, > > On Tue, 19. Jul 2005, at 15:38 -0500, Eric Anderson wrote > according to [mksnap_ffs takes 4-5 minutes?]: > > >>This time, when I ran mksnap_ffs, the command took nearly 5 minutes > > > [...] > > >>Filesystem 1K-blocks Used Avail Capacity iused ifree >>/dev/da1s1d 406234604 91799154 281936682 25% 1300303 51197103 > > > I have a fs here with similar (but smaller size) parameters concerning > inode density and usage: > > Filesystem 1K-blocks Used Avail Capacity iused ifree > /dev/ad1s1d 113390248 92926924 18195520 84% 248434 14424460 > > time mksnap_ffs'ing gives the following result: > 0.007u 1.902s 1:51.94 1.6% 5+217k 4493+8646io 0pf+0w > > It takes almost 2 minutes which seem to perform similarly to your 5 > minutes. > (There was not a single file opened when snapping.) > > I'd expect snapping to speed up by reducing the inode number when doing > newfs, but I haven't verified this right now. A 2tb filesystem with the standard newfs options takes about 30 minutes to mksnap.. That's unusable really, because the filesystem is suspended for so long. Even empty 2tb filesystems take forever, so it's related to the amount of inodes. How can we make this snappier? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------