From owner-freebsd-geom@FreeBSD.ORG Wed May 9 14:16:35 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 7E7DF106564A for ; Wed, 9 May 2012 14:16:35 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 18F608FC18 for ; Wed, 9 May 2012 14:16:34 +0000 (UTC) Received: from OctaHexa64-MkII (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q49EGWou095428 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 9 May 2012 15:16:33 +0100 (BST) Date: Wed, 09 May 2012 15:16:36 +0100 From: Karl Pielorz To: freebsd-geom@FreeBSD.org Message-ID: <1A0908A20F2EDF2BC491695C@OctaHexa64-MkII> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: 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: Wed, 09 May 2012 14:16:35 -0000 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)? Thanks, -Karl