From owner-freebsd-stable@freebsd.org Mon Nov 21 18:16:28 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 2D88DC4CCFC for ; Mon, 21 Nov 2016 18:16:28 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) by mx1.freebsd.org (Postfix) with ESMTP id DBF561DB8 for ; Mon, 21 Nov 2016 18:16:26 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.146] (probe.42.lan [172.29.1.146]) by limbo.b1t.name (Postfix) with ESMTPSA id C6CBA86 for ; Mon, 21 Nov 2016 20:16:16 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=b1t.name; s=mail; t=1479752178; bh=1Oxu5/3QUNqDe5nez0aNhRC2HbvkWF/RG3InL83iOUM=; h=Subject:To:References:From:Date:In-Reply-To; b=uHyyNaN8AN+9X4tFoAR7zSKK4/3VuR/ZvcmoY8EktfrY9463R4Dw1kzREB/dKS79W W05sMk5MqhPbR1/HEN9k3xxscIxJStqv0jczYPoZjfB7mUY//7fZkbIRCmjrqsJp3n D/ybMnuvGUm9f/Th5Exbwoi3A2hp1ye85oYPyPHg= Subject: Re: Help! two machines ran out of swap and corrupted their zpools! To: freebsd-stable@freebsd.org References: From: Volodymyr Kostyrko Message-ID: <583339F0.7050905@b1t.name> Date: Mon, 21 Nov 2016 20:16:16 +0200 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 21 Nov 2016 18:16:28 -0000 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. Good. Try downloading live disc or mfsBSD and importing pool r/o from there. zpool import -N -O readonly=on -f -R /mnt/somezpoool If that doesn't help try: zpool import -N -O readonly=on -f -R /mnt/somezpoool -Fn Drop us a line of your configuration and used ZFS features. Like dedup, snapshots, external l2 logs and caches. -- Sphinx of black quartz judge my vow.