From owner-freebsd-questions@FreeBSD.ORG Sat Jul 20 17:14:15 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F259933D for ; Sat, 20 Jul 2013 17:14:15 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6715BBFD for ; Sat, 20 Jul 2013 17:14:15 +0000 (UTC) Received: from [10.0.0.40] (87.114.92.178.plusnet.thn-ag2.dyn.plus.net [87.114.92.178] (may be forged)) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id r6KHE7eU084606 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 20 Jul 2013 18:14:07 +0100 (BST) (envelope-from frank2@fjl.co.uk) Message-ID: <51EAC56C.4030801@fjl.co.uk> Date: Sat, 20 Jul 2013 18:14:20 +0100 From: Frank Leonhardt Organization: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: to gmirror or to ZFS References: <4DFBC539-3CCC-4B9B-AB62-7BB846F18530@gmail.com> <976836C5-F790-4D55-A80C-5944E8BC2575@gmail.com> <51E51558.50302@ShaneWare.Biz> <51E52190.7020008@fjl.co.uk> <6CE5718E-2646-4D8C-AF98-37384B8851C5@mac.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: frank2@fjl.co.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 17:14:16 -0000 On 16/07/2013 20:48, Charles Swiger wrote: > Hi-- > > On Jul 16, 2013, at 11:27 AM, Johan Hendriks wrote: >>> Well, "don't do that". :-) >> When the server reboots because of a powerfailure at night, then it boots. >> Then it starts to rebuild the mirror on its own, and later the fsck kicks in. >> >> Not much i can do about it. >> >> Maybe i should have done it without the automatic attachment for a new device. > It's normally the case that getting a hot spare automatically attached should be > fine, but not if you also have the box go down entirely and need to fsck. > > I'm more used to needing to explicitly physically swap out a failed mirror component, > in which case one can make sure the system is OK before the replacement drive goes in. > Agreed. Blaming gmirror for this kind of thing overlooks the overall design and operating procedures of the system, and assuming ZFS would have been any better may be wishful thinking. I've had plenty of gmirror crashes over the years, and they have all been recoverable. One thing I never allow it to do is to rebuild automatically. That's something for a human to initiate once the problem has been identified, and if it's flaky power in the data centre the job is postponed until I'm satisfied it's not going to drop during the rebuild. IME, one power failure is normally followed by several more. It's worth noting, as a warning for anyone who hasn't been there, that the number of times a second drive in a RAID system fails during a rebuild is higher than would be expected. During a rebuild the remaining drives get thrashed, hot, and if they're on the edge, that's when they're going to go. And at the most inconvenient time. Okay - obvious when you think about it, but this tends to be too late. Regards, Frank.