From owner-freebsd-fs@FreeBSD.ORG Sun Dec 1 17:29:46 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CB29348 for ; Sun, 1 Dec 2013 17:29:46 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 493AC1111 for ; Sun, 1 Dec 2013 17:29:45 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VnApv-0003Ns-17 for freebsd-fs@freebsd.org; Sun, 01 Dec 2013 09:29:39 -0800 Date: Sun, 1 Dec 2013 09:29:39 -0800 (PST) From: Beeblebrox To: freebsd-fs@freebsd.org Message-ID: <1385918979014-5865165.post@n5.nabble.com> In-Reply-To: <1385761196424-5864850.post@n5.nabble.com> References: <1380880223590-5848720.post@n5.nabble.com> <524EEE40.5060208@gmail.com> <1381060830753-5849397.post@n5.nabble.com> <20131006123350.GJ3287@sludge.elizium.za.net> <1381683172518-5851539.post@n5.nabble.com> <1385711723411-5864713.post@n5.nabble.com> <1385761196424-5864850.post@n5.nabble.com> Subject: Re: Questions re swap-on-zfs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Dec 2013 17:29:46 -0000 Results of testing have producced two problems: 1. The "gconcat label" device does not persist through reboots. I suspect the reason is due to swap #1 being on a zpool (tank0/swap) and this gets mounted before gconcat can do its magic. There's no "canmount=noauto" setting, unless of course I were to disable "org.freebsd:swap=on" (which is probably what needs to be done to make it work). 2. The more important problem however, is one of system freezes during poudriere runs. 4 cores = 4 build jails; during build of larger ports (like firefox, www/webkit-gtk*), if the number of such concurrent builds (large ports) gets to 3, screens freeze, HDD activity continues but eventually produces a kernel panic (I have tried to capture one on dumpdev but no success). If however, the 1G partition is added normally; Device: 1024-blocks Used: /dev/zvol/tank0/swap 4194304 126932 /dev/ada0p1 1048576 126608 I do not get any system freezes and poudriere goes about its business normally. For example: [01]: www/webkit-gtk3 build (00:16:45) [02]: x11/kdelibs4 configure (00:02:45) [03]: www/webkit-gtk2 stage (00:16:23) [04]: graphics/ImageMagick install (00:16:45) Conclusion: gconcat or any other virtual device setup seems doomed to fail and a "real device" seems what's needed for stability. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Questions-re-swap-on-zfs-tp5848720p5865165.html Sent from the freebsd-fs mailing list archive at Nabble.com.