From owner-freebsd-geom@FreeBSD.ORG Thu May 10 03:38:13 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14A0B106564A for ; Thu, 10 May 2012 03:38:13 +0000 (UTC) (envelope-from modulok@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id C46708FC0A for ; Thu, 10 May 2012 03:38:12 +0000 (UTC) Received: by qcsg15 with SMTP id g15so1053715qcs.13 for ; Wed, 09 May 2012 20:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+XPK9ikeq2CdE5PeTp2TfaRmjTDfBphwGdaBCzB102U=; b=rijrO0Sf/5JVKwm6nsq0qqr30ik12H6nT1kC505kBkRN/XrJiUY/8O+KlJ00A3qN39 j0DP2kGQ0xl/QxwW2+atwqSIENNda+7EPkaKofeRnLJbVn3G3rgWxFRjGyAzl3weXtT8 LMXYKtN20i4aLS+gsw3xqPBvRnVb8ahOzX2aBZbb6+pa960NfWEfTriwre4HES+h7bRZ T0vIEXF9KKxRKLHcwga1IwvwRXeh49ij2NhUsPMUUGAPCgF8pageh/A08iZdgycOHXd4 nOVDWdVk+JpRo9tucql8RQspbOA1MnXBNfgsEDErLGG7l0xNGQVXB6pPPP5CL6h6teF/ uK0g== MIME-Version: 1.0 Received: by 10.229.135.84 with SMTP id m20mr1291001qct.96.1336621092062; Wed, 09 May 2012 20:38:12 -0700 (PDT) Received: by 10.229.250.7 with HTTP; Wed, 9 May 2012 20:38:11 -0700 (PDT) In-Reply-To: <1A0908A20F2EDF2BC491695C@OctaHexa64-MkII> References: <1A0908A20F2EDF2BC491695C@OctaHexa64-MkII> Date: Wed, 9 May 2012 21:38:11 -0600 Message-ID: From: Modulok To: Karl Pielorz Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-geom@freebsd.org Subject: Re: FreeBSD 9-R amd64 - graid, should it survive 'pulling' a disk? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2012 03:38:13 -0000 On 5/9/12, Karl Pielorz wrote: > > Hi, > > I've got a Supermicro X8DTL-IF running amd64 FreeBSD 9.0-R, using the > onboard RAID (ICH10 based) and graid, with a RAID 1 mirror comprising of > two Intel 320 series SSD's. > > This works fine - but doesn't survive 'pulling' a disk. I realise this may > not be a 'typical' disk failure scenario (i.e. the device just > "disappearing") - but should it survive? > > At the moment I get a panic with: > > " > (ada0:ahcich0:0:0:0): lost device > g_vfs_done(): raid/r0p4[WRITE(offset=23737925632, length=131072)]error = 6 > /usr3: got error 6 while accessing filesystem > panic: softdep_deallocate_dependancies: unrecovered I/O error > cpuid = 2 > ... > " > > In the middle of the output is: > > " > GEOM_RAID: Intel-441dffb: Disk ada0 state changed from ACTIVE to OFFLINE. > " > > (Which is what you'd expect to see). > > I can get more details - just thought I'd ask to see if this is something > it should just cope with (i.e. having a disk yanked)? Karl, As far as I know, it depends on the disk. I've never used the model mentioned. In my experience, if the disk supports hot swapping then yes, the system should remain up and running when you yank the cable. I've yanked disk cables in a running FreeBSD system which was using Western Digital's RE hot swappable drives without any problems. They were part of a gmirror and on another system a graid3. However, I've also done this on a machine that was using consumer desktop drives and had panics. Perhaps someone else knows more. -Modulok-