From owner-freebsd-fs@FreeBSD.ORG  Mon Jun 15 21:30:33 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.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 7C5C96BA
 for <freebsd-fs@hub.freebsd.org>; Mon, 15 Jun 2015 21:30:33 +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 66A64126
 for <freebsd-fs@FreeBSD.org>; Mon, 15 Jun 2015 21:30:33 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5FLUX3k093679
 for <freebsd-fs@FreeBSD.org>; Mon, 15 Jun 2015 21:30:33 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 199189] SWAP on ZFS can crash server
Date: Mon, 15 Jun 2015 21:30:33 +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.1-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marcus@blazingdot.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-199189-3630-qjBT8SYGkR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199189-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-199189-3630@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-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2015 21:30:33 -0000

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

--- Comment #15 from Marcus Reid <marcus@blazingdot.com> ---
Just another anecdotal observation..  I've got a fresh -CURRENT machine that I
set up with swap on a zvol and am able to get it to fail reliably.  There's a
git process that eats all ram and then goes about 1GB into swap (with 4GB
available) and then swap just appears to stop working. A bunch of processes get
stuck in a pfault state and the box becomes unusable and needs to be reset.

The zvol is set up with compression, dedup, primarycache, sync all off.
Something is definitely still very broken.

My workaround in this case is to use a vnode-backed md device as a swap file,
which is still not ideal but is stable enough until I can rebuild the machine
with normal swap partitions.

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