From owner-freebsd-stable@freebsd.org Wed Dec 9 00:04:35 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 877529D45F4 for ; Wed, 9 Dec 2015 00:04:35 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D38418C8 for ; Wed, 9 Dec 2015 00:04:34 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-184-59-147-149.neo.res.rr.com [184.59.147.149]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id 03792b0f; Tue, 8 Dec 2015 19:04:30 -0500 (EST) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id 60adf49b TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 8 Dec 2015 19:04:30 -0500 (EST) Message-ID: <1449619470.31831.9.camel@michaeleichorn.com> Subject: Re: Periodic jobs triggering panics in 10.1 and 10.2 From: "Michael B. Eichorn" To: Dustin Wenz , freebsd-stable@freebsd.org Date: Tue, 08 Dec 2015 19:04:30 -0500 In-Reply-To: <34FA7D40-8758-460D-AC14-20B21D2E3F8D@ebureau.com> References: <34FA7D40-8758-460D-AC14-20B21D2E3F8D@ebureau.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2015 00:04:35 -0000 On Tue, 2015-12-08 at 16:31 -0600, Dustin Wenz wrote: > I suspect this is a zfs bug that is triggered by the access patterns > in the periodic scripts. There is significant load on the system when > the scheduled processes start, because all jails execute the same > scripts at the same time. > > I've been able to alleviate this problem by disabling the security > scans within the jails, but leave it enabled on the root host. To avoid the problem of jails all starting things at the same time, use the cron(8) flags -j and -J to set a 'jitter' which will cause cron to sleep for a random period of specified duration (60 sec max). Cron flags can be set using the rc.conf variable 'cron_flags'.