From owner-freebsd-bugs@freebsd.org  Wed Dec 16 22:52:53 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 A7B1FA48C53
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 16 Dec 2015 22:52:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 9998B1837
 for <freebsd-bugs@FreeBSD.org>; Wed, 16 Dec 2015 22:52:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBGMqrxg043394
 for <freebsd-bugs@FreeBSD.org>; Wed, 16 Dec 2015 22:52:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 205163] Periodic jobs triggering panics on ZFS host with jails
Date: Wed, 16 Dec 2015 22:52:53 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: dustinwenz@ebureau.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-205163-8-pQrRl66bUz@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205163-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-205163-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 22:52:53 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205163

--- Comment #14 from dustinwenz@ebureau.com ---
I've been unable to reproduce this panic in a test environment, with 60 cloned
jails running periodic jobs every hour. Since the problem occurred often on
production hosts, there might be some other factor that contributes to it. The
only difference that comes to mind is that affected hosts also had other
moderately-sized ZFS filesystem clones (each having several thousand files
totaling between 10 and 100TB per FS) mounted inside of the jails that were
scanned by periodic. Those clones were destroyed and recreated multiple times
daily.

So, I guess my next step is to add some bigger data storage to my test host in
order to make progress on this.

-- 
You are receiving this mail because:
You are the assignee for the bug.