From owner-freebsd-current@FreeBSD.ORG Sun Jun 15 17:25:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28F941065677; Sun, 15 Jun 2008 17:25:56 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id A6CED8FC13; Sun, 15 Jun 2008 17:25:54 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m5FHProw080703; Sun, 15 Jun 2008 21:25:53 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 15 Jun 2008 21:25:53 +0400 (MSD) From: Dmitry Morozovsky To: Kostik Belousov In-Reply-To: <20080615163209.Y43777@woozle.rinet.ru> Message-ID: <20080615211951.W75021@woozle.rinet.ru> References: <20080615130037.J43777@woozle.rinet.ru> <20080615101918.GA94309@deviant.kiev.zoral.com.ua> <20080615161718.R43777@woozle.rinet.ru> <20080615122331.GE94309@deviant.kiev.zoral.com.ua> <20080615163209.Y43777@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sun, 15 Jun 2008 21:25:53 +0400 (MSD) Cc: delphij@freebsd.org, current@freebsd.org Subject: Re: tmpfs panic 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: Sun, 15 Jun 2008 17:25:56 -0000 On Sun, 15 Jun 2008, Dmitry Morozovsky wrote: DM> KB> > KB> I suspect this may be my mistake. DM> KB> > KB> IN case you can reproduce it, please, try the patch below. DM> KB> > DM> KB> > Well, it seems hard to reproduce, possibly some races in kernel memory DM> KB> > allocation exist. Keep trying (run rsync -aH svn tree to tmpfs in the loop) DM> KB> DM> KB> Unmount is required to trigger the problem. Please, report to me whatever DM> KB> your results are. I will commit the patch then. DM> DM> yes, the loop contains rsync, umount, mount. I'll let this run for several DM> hours, then report back to you. With about 80 turns without a panic I think it was great coincidence that I'd encountered this panic. ;-) BTW, side result: 128M for kern.maxswzone is enough for filling tmpfs to 100% under amd64 with 4G RAM + 8G swap. Also, I can observe tmpfs is doing non-optimal; I did not found straight ways to set block/frag size; I suppose for most tmpfs usage they should be decreases to the lowest values, such as 4k/512 -- what do you think? Thanks! Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------