From owner-freebsd-stable@freebsd.org Tue Nov 22 09:39:44 2016 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 D78FEC4F489 for ; Tue, 22 Nov 2016 09:39:44 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72D631160 for ; Tue, 22 Nov 2016 09:39:44 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22c.google.com with SMTP id t79so14990008wmt.0 for ; Tue, 22 Nov 2016 01:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=R32cDR3wHSsqNJEa87dnpo8CPrIkXaDMmQQoK4zhGlU=; b=FT2xjKCqPnrioMdoWrFxWVmY3aAzIIdt4sS7P/SmVYbGoiLVDTUuaFogz6bmlt9cFE o+a61RX+7EWjewQzovBONSGfrELXm3jV8hnCWNobc7j/YTR9UJuxdb0kPjPzyre5DH+g NQ+jMGRTksjZS7dNgZhukDZeSElsDZ8Xnvkh44PUThL0WBFxiY9IRTqvDvx+K7ckYMYm LgkhRLO8mkwOZkBq5S4Rwre2dQqZwSROHYsK94K27FKZAoVJ1tAkBAY7Rr6293HhhFfJ 7qWkNoo/2Q4MAdq+4Qxk7weTOTIZkyx9SMp9jX2FdaWxyeLsrh6g3lM8gh6Ib1+TRHk3 5R7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=R32cDR3wHSsqNJEa87dnpo8CPrIkXaDMmQQoK4zhGlU=; b=Xr1J9haWtOMVTrB7ASSY2S4musSE1Rwkgq7ifKxuINwx3BzCD4Q59jqX6R1h7BCFuP z25g1IP8TLz688f/XxXhpg+dzajMAMmNGv/uX2mwz+tdcUsftL4naO11XhJiwx1A5/9E WUq2WCL38HLd+TIeZR8wF+q4fYEEsz45/q9xjgydvXoU7LRKFsgSowmp924/dH02ATKE bd3Ymua3N2HAhfRHYHmrN8mtQjNjvmU7onFuVNTpYHebgZL2BfF+KFvn8g3UoG6BWx/o a63hwMMvWiU7i05LPNZS8nh0FbpDAMbdqqaqDD0XutS935pfMpR3fox36X5ewBJAGQyc 1qpw== X-Gm-Message-State: AKaTC02ozrCzrbSAT6SpgWQlN/D/xyMJhpnKt9P6aCaiZiE9aGhC2fFbnEWSobjEj4zeL8qH X-Received: by 10.194.236.135 with SMTP id uu7mr13138049wjc.195.1479807582575; Tue, 22 Nov 2016 01:39:42 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id 138sm1916348wms.20.2016.11.22.01.39.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Nov 2016 01:39:40 -0800 (PST) Subject: Re: Help! two machines ran out of swap and corrupted their zpools! To: freebsd-stable@freebsd.org References: From: Steven Hartland Message-ID: <5f4af614-e41a-f59a-ac79-3520b1ed771e@multiplay.co.uk> Date: Tue, 22 Nov 2016 09:40:04 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 09:39:44 -0000 When you say corrupt what do you mean, specifically what's the output from zpool status? One thing that springs to mind if zpool status doesn't show any issues, and: 1. You have large disks 2. You have performed an update and not rebooted since. You may be at the scenario where there's enough data on the pool such that the kernel / loader are out range of the BIOS. All depends on exactly what you're seeing? On 21/11/2016 17:47, Pete French wrote: > So, I am off sick and my colleagues decided to load test our set of five > servers excesively. All ran out of swap. So far so irritating, but whats has > happened is that twoof them now will not boot, as it appears the ZFS pool > they are booting from has become corrupted. > > One starts to boot, then crases importing the root pool. The other doenst > even get that far with gptzfsboot saying it can't find the pool to boot from! > > Now I can recover these, but I am a bit worried, that it got like this at > all, as I havent ever seen ZFS corrupt a pool like this. Anyone got any insights, > or suggstions as to how to stop it happening again ? > > We are swapping to a separate partition, not to the pool by theway. > > -pete. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"