From owner-freebsd-stable@freebsd.org Tue Nov 22 08:39:33 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 A7B17C4F254 for ; Tue, 22 Nov 2016 08:39:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (ingresso-1-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:411::2]) (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 79595F6B for ; Tue, 22 Nov 2016 08:39:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c96c0-000ISR-3Q; Tue, 22 Nov 2016 08:39:32 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c96bz-0004uQ-Vx; Tue, 22 Nov 2016 08:39:32 +0000 To: crest@rlwinm.de, freebsd-stable@freebsd.org Subject: Re: Help! two machines ran out of swap and corrupted their zpools! In-Reply-To: Message-Id: From: Pete French Date: Tue, 22 Nov 2016 08:39:31 +0000 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 08:39:33 -0000 > How much trust do you put in your hardware? Have you ever put the > hardware under full load for extended periods before e.g. run poudriere > to build pkg repos? Ah, now that is a good point. There are two drves in each machine, mirrored, but one of each of the pair is 6 years old. We havent seen any errors, but that doesnt mean it wouldnt errpr under test. On the other hand I would epect only one drive to be corrupt in that case though, and booting from the otherdrive still shows the same problems. But that may be due to ZFS finding both drievs and trying to use them as a pair ? Am not sure how far into the boot sequence it starts using more tha just the drive it was booted from.... -pete.