From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 16:09:20 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EB1A0B75 for ; Mon, 30 Mar 2015 16:09:20 +0000 (UTC) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B84D6897 for ; Mon, 30 Mar 2015 16:09:20 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id B40081308 for ; Mon, 30 Mar 2015 12:09:16 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Mon, 30 Mar 2015 12:09:19 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=gcEhBRj6SAhYpyW QyyG60I4WRco=; b=GYHsbjiZQOs+TnCfSQeHQacd5QiOpbsF8XFGs1oKTvyYge/ 1ueIwY1UFLvr8yad99S/meWqwtSdvTNhsVet2uCn0Hc13RjIuV/AjeskQlscoIKE lKkiDaI5fPczSKHoQiCS021EDEx7VnSikTIUVNA9qPdRl64m4hXvPfZtIluo= Received: by web3.nyi.internal (Postfix, from userid 99) id 5AD1510C486; Mon, 30 Mar 2015 12:09:19 -0400 (EDT) Message-Id: <1427731759.309823.247107417.308CD298@webmail.messagingengine.com> X-Sasl-Enc: vXJtnszXY9NpZw+QK9YECx2yITMYdLE9WkVdytgYZpZX 1427731759 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 Subject: Re: Little research how rm -rf and tar kill server Date: Mon, 30 Mar 2015 11:09:19 -0500 In-Reply-To: <5519740A.1070902@artem.ru> References: <55170D9C.1070107@artem.ru> <1427727936.293597.247070269.5CE0D411@webmail.messagingengine.com> <55196FC7.8090107@artem.ru> <1427730597.303984.247097389.165D5AAB@webmail.messagingengine.com> <5519716F.6060007@artem.ru> <1427731061.306961.247099633.0A421E90@webmail.messagingengine.com> <5519740A.1070902@artem.ru> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 16:09:21 -0000 On Mon, Mar 30, 2015, at 11:04, Artem Kuchin wrote: > 30.03.2015 18:57, Mark Felder =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > > On Mon, Mar 30, 2015, at 10:53, Artem Kuchin wrote: > >> This is normal state, not under rm -rf > >> Do you need it during rm -rf ? > >> > > No, but I wonder if changing the timer from LAPIC to HPET or possibly > > one of the other timers makes the system more responsive under that > > load. Would you mind testing that? > > > > You can switch the timer like this: > > > > sysctl kern.eventtimer.timer=3DHPET > > > > And then run some of your I/O tests > > >=20 > I see. I will test at night, when load goes down. > I cannot say sure that's a right way to dig, but i will test anything :) >=20 > Just to remind: untar overloads the system, but untar + sync every 120s=20 > does not. > That seems very strange to me. I think the problem might be somewhere > here. >=20 I just heard from mav that there was a bottleneck in gmirror/graid with regards to BIO_DELETE requests https://svnweb.freebsd.org/base?view=3Drevision&revision=3D280757