From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 12 17:12:31 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00D2C1065675 for ; Fri, 12 Sep 2008 17:12:31 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id CBA828FC23 for ; Fri, 12 Sep 2008 17:12:30 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 42CB31A000B38 for ; Fri, 12 Sep 2008 10:12:30 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jpPHbJjMIY9C for ; Fri, 12 Sep 2008 10:12:20 -0700 (PDT) Received: from coal (unknown [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id B0C711A012070 for ; Fri, 12 Sep 2008 10:12:10 -0700 (PDT) From: Freddie Cash To: freebsd-hackers@freebsd.org Date: Fri, 12 Sep 2008 10:12:09 -0700 User-Agent: KMail/1.9.9 References: <5f67a8c40809120904o49b6e410l5b65a20f5216202@mail.gmail.com> <20080912163207.GE60094@icarus.home.lan> In-Reply-To: <20080912163207.GE60094@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809121012.10195.fjwcash@gmail.com> Subject: Re: ZFS w/failing drives - any equivalent of Solaris FMA? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2008 17:12:31 -0000 On September 12, 2008 09:32 am Jeremy Chadwick wrote: > For home use, sure. Since most home/consumer systems do not include > hot-swappable drive bays, rebooting is required. Although more and > more consumer motherboards are offering AHCI -- which is the only > reliable way you'll get that capability with SATA. > > In my case with servers in a co-lo, it's not acceptable. Our systems > contain SATA backplanes that support hot-swapping, and it works how it > should (yank the disk, replace with a new one) on Linux -- there is no > need to do a bunch of hoopla like on FreeBSD. On FreeBSD, with that > hoopla, also take the risk of inducing a kernel panic. That risk does > not sit well with me, but thankfully I've only been in that situation > (replacing a bad disk + using hot-swapping) once -- and it did work. Hrm, is this with software RAID or hardware RAID? With our hardware RAID systems, the process has always been the same, regardless of which OS (Windows 2003 Servers, Debian Linux, FreeBSD) is on the system: - go into RAID management GUI, remove drive - pull dead drive from system - insert new drive into system - go into RAID management GUI, make sure it picked up new drive and started the rebuild We've been lucky so far, and not had to do any drive replacements on our non-ZFS software RAID systems (md on Debian, gmirror on FreeBSD). I'm not looking forward to a drive failing, as these systems have non-hot-pluggable SATA setups. On the ZFS systems, we just "zpool offline" the drive, physically replace the drive, and "zpool replace" the drive. On one system, this was done via hot-pluggable SATA backplane, on another, it required a reboot. -- Freddie Cash fjwcash@gmail.com