From owner-freebsd-amd64@freebsd.org  Fri Jan 15 17:25:56 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 08AF8A8356D
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Fri, 15 Jan 2016 17:25:56 +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 EE5F114AD
 for <freebsd-amd64@FreeBSD.org>; Fri, 15 Jan 2016 17:25:55 +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 u0FHPtx1024801
 for <freebsd-amd64@FreeBSD.org>; Fri, 15 Jan 2016 17:25:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 205708] Kernel panic possibly happening while
 adding/removing/listing ZFS snapshot
Date: Fri, 15 Jan 2016 17:25:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: root_dfjo1hpy@meo.ws
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-205708-6-f5ATGU1X4Q@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205708-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-205708-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 15 Jan 2016 17:38:51 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 17:25:56 -0000

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

--- Comment #7 from Fusl <root_dfjo1hpy@meo.ws> ---
Hi,

sorry for not updating this earlier.

I upgraded the memory of this machine from 36GB (5*4GB + 4*GB modules) to 7=
2GB
(9*8GB) memory and it seems to be more stable now (not a single issue since
then):

[root@chernobyl:~] uptime
 5:17PM  up 14 days,  2:39, 5 users, load averages: 0.23, 0.24, 0.30
[root@chernobyl:~] sysctl vfs.zfs.l2arc_noprefetch
vfs.zfs.l2arc_noprefetch: 0
[root@chernobyl:~] zfs get -Hovalue sync,logbias data
disabled
throughput

Since this is a production environment I would rather like to keep the syst=
em
running like that. However, if the system happens to crash another time I w=
ill
try to update and/or apply the patch.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=